Error responses: remove OUT_OF_RANGE, clarify 404, and use the common error responses and examples #29

Problem description

The error responses in device-authenticity.yaml are all defined locally, with inline examples. Some of them do not fit the API:

• 400BadRequest allows OUT_OF_RANGE, and the error list in info.description documents it. The API has no range-restricted fields: the only input is imei, with a fixed pattern.
• 404NotFound returns IDENTIFIER_NOT_FOUND for "IMEI not found in any accessible database". However, info.description defines that an IMEI not present on any list results in status unknown. It is unclear when a 404 is returned instead of a 200 response with unknown.
• None of the error examples reference the shared examples in CAMARA_common.yaml. All of them are defined inline.

Expected behavior

Following the CAMARA API Design Guide section 3.2, an error response either references a common error response, or is defined locally with exactly the codes the API returns and with examples referenced from components/examples of CAMARA_common.yaml:

Update the error list in info.description and the test definitions accordingly.

Additional context

• CAMARA_common.yaml (r4.4)
• Related: Use references to the common definitions of Commonalities r4.4 where possible #30 (references to the common schemas)
• To be done before the next release after r1.1 (or before it - codeowners choice).