SET-385 Allow archiving of sequencing groups via metamist api

[dancoates]

This implementation allows for simple archiving of sequencing groups.
While this is not something that needs to happen often, there are cases
where sequencing groups are replaced by other samples and are not
automatically archived. In those cases it can be necessary to manually
archive the sequencing groups and also the sample and analysis. Sample
and analysis both already allow their "active" property to be updated so
sequencing groups were the odd one out by not allowing
deactivation/archiving.

[codecov]

Codecov Report

Attention: Patch coverage is 90.90909% with 3 lines in your changes missing coverage. Please review.

Project coverage is 82.94%. Comparing base (f569d82) to head (ac23d98).
Report is 1 commits behind head on dev.

Files with missing lines	Patch %	Lines
api/routes/sequencing_groups.py	40.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1020      +/-   ##
==========================================
+ Coverage   82.92%   82.94%   +0.01%     
==========================================
  Files         191      191              
  Lines       16758    16788      +30     
==========================================
+ Hits        13897    13924      +27     
- Misses       2861     2864       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[amyminiter]

Thanks so much @dancoates for implementing this so quickly.

A note only: we discussed inconsistencies between naming for boolean attributes for analysis (active) and sg ('archived'. This implementation does maintain those inconsistencies but updating that seems like a larger piece of work for another time.

[amyminiter]

😄

[dancoates]

A note only: we discussed inconsistencies between naming for boolean attributes for analysis (active) and sg ('archived'. This implementation does maintain those inconsistencies but updating that seems like a larger piece of work for another time.

Yeah, always tricky to manage backwards compatibility with this sort of stuff, we can't just go through and rename everything to be consistent. Potentially we could support both archived and active but as you say it is probably a larger piece of work where we consider the implications of changing the status of each type of entity and how things cascade.