feat: Allow disabling data use terms

[fhennig]

resolves #3127

preview URL: https://disable-dut.loculus.org

Summary

• Adds a new config value dataUseTermsEnabled (Potentially BREAKING the way it works now, maybe should just default to true in the Chart? - https://loculus.slack.com/archives/C05G172HL6L/p1738166112981629)
• DUT stuff gone on the submit dialog
• DUT note gone on the API docs page
• TODO: On the 'View' page for my groups sequences, hide the 'Edit data use terms' button (for bulk editing)
• TODO(maybe): on the individual sequence page, disable the button for editing data use terms?

Testing

• Frontend: Added a test that submission is possible when DUT is disabled
• TODO Backend: Test that the submit endpoint can be called without the DUT type now (if disabled) and test that an error is raised if it is omitted but is required.
• TODO Backend: Add a test that the DUT related things are not returned by get-released-data

Screenshot

The submission dialog without the DUT elements:

The API docs don't mention the DUT anmore:

PR Checklist

• All necessary documentation has been adapted.
• The implemented feature is covered by an appropriate test.

[fhennig]

As was discussed earlier, here are the code places marked where I think changes will be introduced to implement this feature.

@corneliusroemer you wanted to have a look first. Putting this on hold till then.

cc @chaoran-chen

[theosanderson]

Would the backend not need any changes?

[fhennig]

That wasn't in the ticket I think. But maybe that was a mistake? I remember that we talked about that too actually. I'd be curious to look into how to do that

[theosanderson]

My guess (maybe wrong) of what would happen if you made the changes annotated would be:

• backend would still expect data use terms on submission so would give an error
• backend would still emit data use terms in get-released-data so SILO would get confused at the unexpected field

[chaoran-chen]

We need to do some changes so that (1) the backend accepts submissions that don't provide a data use term and (2) don't expose it in get-released-data. But if it make things easier, it could write "open" into the database.

[fhennig]

Ah, makes sense

[fhennig]

that should cover it.

[fhennig]

I tried quite some time to get the "Submit" button to move to the end of the page, but I couldn't do it without making changes to the BaseLayout and so I'll just leave it for now. If you think it's important then I'll spend some more time on it, but maybe we can also leave it.

[theosanderson]

(I actually don't like huge gaps between the submit button and everything else!)

[fhennig]

perfect! 😄