feat(website): add revise form

[theosanderson]

resolves #3092

preview URL: https://revise-form.loculus.org/

Summary

I don't currently understand how a test could be added in our current paradigm: #1315

[anna-parker]

@theosanderson this looks amazing - yesterday I tested a bit but the preview went down. I am documenting my testing here now:

Testing comments:

• LOC_000PD32.1: revised metadata
• LOC_000PD24.1: revised sequence
• LOC_000PCWG.1: revised metadata and sequence

Confirmed these were not overwritten by ingest during reingest: this is due to the hash not being changed by the form:

Furthermore, the form doesn't even allow curators to change the hash (this isn't a listed field), so using this approach we will not run into: #3084 - we only need to make sure that ingest can handle the edge case in #3085 (or if a superuser accidentally curates via the revise page and doesn't use original metadata).

[anna-parker]

Hi Theo! This looks really great! Also the tests I did look good I was wondering though if you could still verify my understanding a bit.
So here when you call the editPage when clicking the revise button - am I correct in understanding this is sending a get-data-to-edit request to the backend? (e.g. here: https://github.com/loculus-project/loculus/blob/1b7ce069b9b51e8e23d5ec000aa96365318eeab5/website/src/pages/%5Borganism%5D/submission/edit/%5Baccession%5D/%5Bversion%5D.astro#L17C49-L17C62 - which gets the processed and original data from the backend for that sequence) - but we only display the original metadata that is specified in EditableOriginalDataProps.inputFields which comes from the config.

[theosanderson]

That sounds about right! (Mostly the behaviour is just like the old edit page, just that it submits differently for the revision case and displays a different header!)