Y26-041 - Send updated Retention Instructions to Traction

[KatyTaylor]

User story

As a Long Read user, I would like any Retention Instructions updated in Sequencescape to propagate to Traction, to make sure the data is in sync.

Who are the primary contacts for this story

Katy, Ben, Emily A

Who is the nominated tester for UAT

Emily A, once Traction side is also done

Acceptance criteria

Consider if these features can be featured flagged to decouple testing and deployment.
To be considered successful the solution must allow:

When

• Retention Instructions are updated via the UI, or
• Retention Instructions are updated via manifest re-upload,

Then

• API call is sent to Traction Service endpoint (developed in Y26-040 - Endpoint for updating Retention Instructions traction-service#1785)
• Payload includes a list of affected labware barcodes (just one if updated via UI)
  • These should be the human-readable form, not the machine-readable form, as Traction cannot translate between the two.
• Payload includes the new Retention Instruction value for each labware barcode
• Failure case is handled gracefully, with retries and final notification to user and PSD if still failing - this could be via Delayed Jobs.
• Not necessary to provide feedback to the user upon success, only failure.

Dependencies

Won't be useful until sanger/traction-service#1785 is done, but doesn't need to be blocked if a) rejected API calls are handled gracefully, or b) feature flagged.

Additional context

See parent research story and architectural decision record.

Deployment notes

Add any details that should be noted when deploying this feature. For example, is a database migration needed, a specifc rake task or other script that needs to be run, a dependency on another application or service that needs to be released first etc?
These notes are intended to ensure the developers releasing the feature know what needs to be done.

Add any other context or screenshots about the feature request here.