fix(backend): scope current pipeline etag tracker by organism

[clonder]

Fixes released-data ETag invalidation for current_processing_pipeline.

Pipeline changes for one organism no longer invalidate released-data cache checks for other organisms.

Fixes #6698 and related to #5110

🚀 Preview: Add preview label to enable

[theosanderson]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: 5cf0327ad8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[anna-parker]

Looks great! Sorry for the delay in reviewing!

This isnt really necessary as we have tests and we have confirmed the tracker is working. But if you would like to get a feeling for how reprocessing works you could test this out on a preview and look into the grafana logs

• add the preview label to the PR
• Id recommend setting the preview db to persistent by adding developmentDatabasePersistence: true to your values.yaml
• After all sequences are ingested on the preview doing a pipeline version bump for one organism e.g. ebola
• Then you can confirm that there is no change in the etag of other organisms (you can see this best in the silo-import logs), they will show that if the etag changed or not:

On Wednesday we can set up your kubeconfig so that you can portforward to preview databases as well :-)