Y24-160 - Update labware processor to facilitate retention instructions

[dasunpubudumal]

User story As developers, we need to facilitate sending retention instructions for labware (each tube/plate submitted) to mlwh by updating tol_lab_share/processors/create_labware_processor.py to support the retention_instruction field in the schema.

Who are the primary contacts for this story Steve / Stuart / Dasun

Who is the nominated tester for UAT

Acceptance criteria To be considered successful the solution must allow:

• [x] All messages received on the current message schema version are treated as implicitly specifying "Return to customer after 2 years" for the retention field.
• [x] All messages received on the new message schema version must contain retention_instruction field.
• [x] tol-lab-share should be able to process messages coming from either version of the schema.
• [x] Update lab-share-lib to allow validating the messages for a given list of schemas.

Dependencies This story is blocked by the following dependencies:

• https://github.com/sanger/General-Backlog-Items/issues/412

References This story has a non-blocking relationship with:

• https://github.com/sanger/tol-lab-share/issues/85

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

[dasunpubudumal]

Note: How does traction-service push messages to warehouse?

traction-service has got a sidecar broker (accessible via http://trac-uat.psd.sanger.ac.uk:15672/) that has the shovel plugin installed.

traction-service publishes messages to its own broker, which the shovel plugin delivers to the psd.sequencescape exchange in the warehouse which is bound to the queue psd.mlwh.multi-lims-warehouse-consumer (via a routing key). This will be consumed by warren and unified_warehouse and will persist the data in mlwh.

The overall process explained: