Alignment of CAMARA_common.yaml 'device' description with the removal of 'IDENTIFIER_MISMATCH'

[PedroDiez]

Problem description
In MetaRelease Fall25, IDENTIFIER_MISMATCH exception is removed. In other words, when an API Client indicates more than one identifier for a device, API provider will take one of them for the API logic, without performing any matching checking among identifiers provided by API client.

Reference:
Remove 422 IDENTIFIER_MISMATCH error code as this can allow PII leakage

In CAMARA_Common.yaml it is reflected for device object:

NOTE1: the network operator might support only a subset of these options. The API invoker can provide multiple identifiers to be compatible across different network operators. In this case the identifiers MUST belong to the same device.

And this is misleading, because now the API logic does not perform any matching among them so as it is not an issue nor a requirement that they MUST belong to the same device.

Expected behavior

It is proposed to update NOTE1 as below:
Replace In this case the identifiers MUST belong to the same device. by In this case the API Provider will consider one of them for the API logic, without performing any matching checking among the provided identifiers.

Other option would be just Remove In this case the identifiers MUST belong to the same device.
Nonetheless think that previus one is more detailed and transparent.

Alternative solution
N/A

Additional context
N/A