refactor(website): Split fetching of backend and lapis sequence details in findOrganismAndData

[tombch]

Summary

• The findOrganismAndData function is used in the website to retrieve sequence details when viewing sequences both in the search UI and on an individual sequence details page for an accession. Previously, this function called getSequenceDetailsTableData for each organism, which would query LAPIS (for sequence details) and the backend (for data use terms history). The backend calls were duplicated across organisms when only a single call needs to be made.
• This PR refactors the findOrganismAndData and getSequenceDetailsTableData to keep the fan-out approach for LAPIS queries, but have a single call to all required backend endpoints. It does this by splitting the LAPIS and backend data fetching into separate getLapisSequenceDetails and getBackendSequenceDetails functions.
• With the getBackendSequenceDetails now called once rather than per-organism, we add the sequence citation fetching to the getBackendSequenceDetails, to remove some duplicated code.

Screenshot

PR Checklist

• All necessary documentation has been adapted.
• The implemented feature is covered by appropriate, automated tests.
• Any manual testing that has been done is documented (i.e. what exactly was tested?)

🚀 Preview: Add preview label to enable