Review and fix documented error response codes

[eric-murray]

Problem description
Some of the documented error response codes are either invalid codes, or are valid codes that would not be returned by this API.

Invalid code - not defined by the Commonalities Design Guide:
422 UNIDENTIFIABLE_APPLICATION_PROFILE

Error response codes that do not appear to apply to this API:
400 OUT_OF_RANGE (for some endpoints)
403 INVALID_TOKEN_CONTEXT
404 IDENTIFIER_NOT_FOUND
404 NOT_FOUND (for some endpoints)
422 SERVICE_NOT_APPLICABLE

Expected behaviour
API specific error codes should be defined according to the Commonalities Design Guide. In this case, probably:
422 APPLICATION_ENDPOINT_REGISTRATION.UNIDENTIFIABLE_APPLICATION_PROFILE

But why is this not 404 NOT_FOUND? Please document.

Error response codes that cannot be returned should be removed from the API definition.

API specific conditions that trigger each documented error response should also be documented where these are not documented by Commonalities.

Alternative solution
None

Additional context
None

[maheshc01]

Removed inapplicable error codes:

• 422 removed from all endpoints — SERVICE_NOT_APPLICABLE, MISSING_IDENTIFIER, UNSUPPORTED_IDENTIFIER are all device-identifier codes; this API has no device identifier
• 403 INVALID_TOKEN_CONTEXT removed — per the Design Guide, this SHOULD only be used when the API can confirm token/identity match; not applicable here
• 404 IDENTIFIER_NOT_FOUND removed — device-specific code, not applicable
• 400, 404 removed from GET /application-endpoint-lists — no request body, no path params, no specific resource lookup
• 422 UNIDENTIFIABLE_APPLICATION_PROFILE removed — not a Commonalities standard code; the scenario is handled by the standard 404 NOT_FOUND

Generic422 component removed entirely — all codes it contained were device-identifier specific.