⛔️ add a DEPRECIATED status for analyses, that once where SUCCEEDED but should not be used

[juanesarango]

From @nickp60:

We are trying to depreciate certain analyses so they are ignored when trying to run downstream apps, but have them be available for the other queries like getting the results or metadata. We are considering adding a custom_field for depreciated in the analysis object. We could just run all the apps with a -fi custom_fields.depreciated false to exclude those analyses, but it would be nice if we could configure the api to automatically add that to app queries.

From Mirae Baichoo:

... if run on the sample level - we might have some analyses that were run on a smaller number of sequencing files, but then a new sequencing result was returned and we run the analyses again). We would like to keep the old analyses but consider them "depreciated".

This use case is for example when same Application has different analyses with different number of Targets, and you want to flag as depreciated the previous run.

A good solution would be to mark previously SUCCEEDED and protected analyses, as DEPRECIATED, to avoid these being used by downstream analyses that depend on those results.