feat(backend, website): Use version comments field for revocations as well.

[anna-parker]

resolves #2345, #640

preview URL: https://version-comments.loculus.org/

Summary

1. Add version_comments metadata field to values.yaml -> this will show up on the details page (this is done in feat(config): Add version_comment field to be used when revising sequences. #2355) This is still working:

2. Also let revocations use this field. Need to add a revocation_comments field to the revoke endpoint and also update the website where used. Then this value needs to be shown on the webpage. The webpage gets its metadata from LAPIS, which in turn gets it from the backend. LAPIS periodically queries the backend using "/get-released-data". I add the revocation_comments field here as version_comment for revocations.
3. Test with having the webpage always add the same string when revoking - works:

4. Optionally add reason on webpage:
   
   which is then correctly added to version_comments:

Also added on revocationentrydatatable: 

Screenshot

PR Checklist

• Adapt revocation form to allow comments
• Figure out why the website keeps getting stuck locally - I can test the backend and postgres but the webpage is stalling weirdly.
• Fix backend tests

[theosanderson]

To my mind wherever we use this column we could call it "version comment" – I don't see that we ever need to use the naming "revocation comment" (even though it may apply to a revocation – a revocation is still a version)

[anna-parker]

Fixed: Error: org.loculus.backend.service.submission.SequenceEntriesView.revocation_comments is not in record set

[theosanderson]

Really nice

[fengelniederhammer]

IMO the backend is missing a test that checks that the comment can be provided and that it is visible then somewhere else.

[fengelniederhammer]

I didn't properly check the website part, but the Kotlin part looks good to me.