Add 'archive' boolean to all the thngs

[jeromegv]

Reasoning is that we don't want to totally delete elements. Before adding those new "archive" elements, we should well understand the whole flow of how it will be managed from a UI perspective, to be sure that whatever we change in the model do make sense. We might just change the model of the SOC (for achived SOC) and only use the API to check if a tag or datapoint is active (by looking at the SOC associated). To be rediscussed

[jeromegv]

After some planning on my side, I think what makes the most sense is that when we Archive a full SOC, we do a query for all datapoints and tags associated with that SOC and add a field "SOC Archived" (or similar). If we want to archive a tag or a datapoint independently, it must be done by adding a tag "Archived" (different from the formed). That way, if later we want to re-enable a SOC, the tags and datapoints that were archived independently will stay archived. So when we want to query a tag or a datapoint, we can look at the record to know if it's archived, if its SOC archived, or just normal.

[jeromegv]

todo: add confirmation dialog before archiving todo later: interface to manage archived objects