Add the `deprecated` property to locations

[danse]

In the call centre, a deprecated property is used in order to show legacy locations, without allowing them to be used for new data. This allows to perform breaking changes smoothly, in two steps:

• deprecate old location, insert new, release
• migrate data in the database (optional)
• remove old location, release (optional)

This way, migrations do not need to be synchronised with new releases.

This property has to be added to the data model

[febeling]

Yes, correct. Step 2-3 are optional though, I'd argue.

[emig]

Optional and good to have, correct.

[febeling]

The important win imho is, that any requirement for synchronous migration and deployment of new location sets is lifted. That's mostly why I mention the optional nature.

[emig]

it is a good comment, will edit that