Commonalities pass for corrections

[caubut-charter]

Problem description
Take another pass at commonalities looking for alignment corrections needed.

Expected behavior

Alternative solution

Additional context
Example to look at: https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#appendix-a-infodescription-template-for-device-identification-from-access-token

[caubut-charter]

Error codes also in this pass: https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#61-standardized-use-of-camara-error-responses

[hdamker]

Error codes also in this pass: https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#61-standardized-use-of-camara-error-responses

For this you can copy/paste from https://github.com/camaraproject/Commonalities/blob/main/artifacts/CAMARA_common.yaml

In addition you might want to consider which operation are "allowed" to return a 501 (NOT_IMPLEMENTED). There was a TSC discussion about camaraproject/Commonalities#246 with the result that "Mandatory endpoints must not have 501 defined as a valid response". Currently you have defined 501 as a potential response for all operations, but I don't think you want to indicate that the implementation of all these endpoints is "optional".

[hdamker]

Another point for your pass: mandatory header x-correlator in every request and response, cf. https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#9-architecture-headers

[RandyLevensalor]

Add 3-legged device identification in the info object and the relevant api call / schemas.

https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#appendix-a-infodescription-template-for-device-identification-from-access-token