GPL-595 Track released samples in Lighthouse DB [s]

[emrojo]

User story
Any labware released from Lighthouse into Sequencescape will have set its values for all SS process; there is the possibility that the lighthouse files are updated and changed it values, which it could trigger updating Lighthouse database, but not SS after this sample has been released.
At the moment the only way to know if a sample has been released to Sequencescape is to check that the labware exists in SS database; it could be useful to know from Lighthouse when a sample has already been released in order to avoid updating its values from crawler, and also trigger an error in the situation when a file from crawler tries to change its value.

Who are the primary contacts for this story
Eduardo Martin
Andrew Sparkes

Acceptance criteria
To be considered successful the solution must allow:

• Store released_at as a timestamp of the moment when a sample has been released into SS
• Trigger a notification error when there is an attempt of updating the values of a sample that has already been released, so it needs to be look into.

Dependencies
This story is blocked by the following dependencies:

• #<issue_no.>
• sanger/#<issue_no.>

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