Enable hiding deprecated tags in the tooling

See parent for context.

We want to add a new boolean field to the TagManager DB so tags can be marked as "deprecated" (name TBC) - IE they still exist, but the UI should not offer them as options to add to new articles.

**update**
CAPI keeps an index of tag, kept up to date by consuming a kinesis stream that TagManager posts to. To avoid needing to re-index en masse at a later date, we want the new property to be incorporated into CAPI's tag model before Tagamanager can set the property in production.

If we don't include the property in CAPI, it might hinder future work to switch to using CAPI as the data source for tag in tooling.

**tasks**:
- decide on name for the field (leaning towards "deprecated", but with a more user-friendly display name in the UI)
- update [tags-thrift-schema ](https://github.com/guardian/tags-thrift-schema) to include the new property and update CAPI to use the new model
- add field to the DB (Tag manager uses Dynamo, so we should not need to update a schema)
- expose the field on the internal API
- include the field in the tag update events posted to [porter](https://github.com/guardian/content-api/tree/main/porter)
- expose the field on the hypermedia API consumed by workflow and Composer, test on code to ensure this doesn't caused and problems downstream (EG consumers do not fail to parse the api response)