keeping track of name/id changes in instances

[lzehl]

If an instance changes its name it typically also affects the atid which affects automation (in EBRAINS but also for the auto-population pipeline).

Discussion in the team resulted in the following solution:

Add "owl:sameAs" to instances that do change the ID and list there all alternative (old) identifiers.

DEPR: "@id": "https://openminds.ebrains.eu/instances/contentTypes/4-mat"
v3.0: "@id": "https://openminds.ebrains.eu/instances/contentTypes/application_4-mat"
latest: "@id": "https://openminds.om-i.org/instances/contentTypes/application_4-mat"
->
latest:

{
  "@context": {
    "@vocab": "https://openminds.om-i.org/props/",
    "owl": "http://www.w3.org/2002/07/owl#"
  },
  "@id": "https://openminds.om-i.org/instances/contentTypes/application_4-mat",
  "@type": "https://openminds.om-i.org/types/ContentType",
  "owl:sameAs": [
    "https://openminds.ebrains.eu/instances/contentTypes/4-mat",
    "https://openminds.ebrains.eu/instances/contentTypes/application_4-mat"
  ]

@openMetadataInitiative/openminds-developers do we do this as well if the attype is changing?
v3.0: "@id": "https://openminds.ebrains.eu/instances/technique/T1"
latest: "@id": "https://openminds.om-i.org/instances/MRIWeighting/T1"
->
latest:

{
  "@context": {
    "@vocab": "https://openminds.om-i.org/props/",
    "owl": "http://www.w3.org/2002/07/owl#"
  },
  "@id": "https://openminds.om-i.org/instances/MRIWeighting/T1",
  "@type": "https://openminds.om-i.org/types/MRIWeighting",
  "owl:sameAs": [
    "https://openminds.ebrains.eu/instances/technique/T1"
  ]