feat(website): display version comment on review cards for revocations

[theosanderson-agent]

Summary

Fixes #6394 (and addresses #4522).

Previously, when reviewing a revocation entry on the review page, there was no way to see the version comment the submitter entered when creating the revocation. The card only showed a generic message: "This is a revocation entry, which will create a new version that revokes this accession". This made it impossible to double-check the revocation reason before approving the entry.

This PR surfaces the version comment alongside the existing revocation marker on the review card.

Changes

Backend

• Add versionComment: String? to SequenceEntryStatus (SubmissionTypes.kt).
• In getSequences (SubmissionDatabaseService.kt), extract the value from unprocessed_data.metadata.versionComment using a JSONB scalar path. After the V1.27 migration the comment lives there for revocations.

Website

• Add versionComment to the sequenceEntryStatus zod schema.
• Render a Version comment KeyValueComponent on the review card whenever the entry is a revocation and a comment was provided.
• Add a Vitest case asserting the comment is rendered for revocation entries.

Design notes

• The existing /get-data-to-edit endpoint (used by useGetMetadataAndAnnotations to populate the review card's metadata) explicitly errors for revocations, so it was not appropriate to repurpose. Returning the comment on the list response means no extra HTTP round-trip per card.
• For non-revocation revisions, versionComment is already part of the processed metadata and rendered via the existing MetadataList. The new card field is gated on isRevocation to avoid showing it twice.

Test plan

• Manual check: submit a revocation with a version comment, open the review page, confirm the comment is shown on the card.
• Manual check: submit a revocation without a comment — no "Version comment" row appears (only the existing revocation marker).
• Manual check: revisions still show their versionComment via the normal metadata list (unchanged behavior).
• CI=1 npm run test (website) — 646 tests passing including new should show the version comment for revocation entries case.
• CI=1 npm run check-types (website) — clean.
• npm run format (website) — clean.
• ./gradlew compileKotlin && ./gradlew ktlintFormat (backend) — clean.
• Backend integration tests — could not run locally (test infra needs Docker/postgres setup); rely on CI.

🤖 Generated with Claude Code

🚀 Preview: Add preview label to enable

[theosanderson]

Details

> The existing /get-data-to-edit endpoint (used by useGetMetadataAndAnnotations to populate the review card's metadata) explicitly errors for revocations, so it was not appropriate to repurpose. Returning the comment on the list response means no extra HTTP round-trip per card.

@theosanderson-agent Try making an alternative PR which: renames this endpoint to /get-original-data-for-entry and makes it not error for revocations and uses that instead

[theosanderson-agent]

Opened #6412 as the alternative you suggested: /get-data-to-edit/{accession}/{version} is renamed to /get-original-data-for-entry/{accession}/{version}, the endpoint no longer throws 422 for revocations, and the review card now reads versionComment from originalData.metadata instead of a new field on /get-sequences. SequenceEntryVersionToEdit.processedData becomes nullable (null for revocations) and isRevocation is added to the response. CLI / integration auth test / website client all updated to the new path.

Happy to close this PR in favour of #6412 if that approach looks right.