Alignment of QoD APIs with Commonalities release r2.2

[hdamker]

Problem description

Release r2.2 (0.5.0-rc.1) of Commonalities introduces some additional changes compared to the alpha release:

• Common artifacts for testing error scenarios for device and phoneNumber by @jlurien in Common artifacts for testing error scenarios for device and phoneNumber Commonalities#325
  • In work in Use common artifact for device test scenarios #400
• ACCESS_TOKEN_EXPIRED termination reason guidance by @bigludo7 in Provide ACCESS_TOKEN_EXPIRED termination reason guidance Commonalities#364
  • Already done in Clarify sinkCredentials expiration #396
• String pattern added to x-correlator scheme by @rartych in String pattern added to x-correlator scheme Commonalities#373 and updated in Allow zero-length strings in x-correlator header Commonalities#387
• Subscriptions and Notifications artifacts errors aligned with enum values by @PedroDiez in Subscriptions and Notifications artifacts errors aligment -enum values- Commonalities#361
• Guidelines on non-mandatory error statuses, 429 made non-mandatory and special considerations for 501 by @rartych in Clarification on non-mandatory error statuses, 429 made non-madatory Commonalities#374
• Changed guidelines on x-camara-commonalities extension field by @rartych in Change guidelines on x-camara-commonalities extension field Commonalities#375
  • will be addressed in release PR
• Improved 403 INVALID_TOKEN_CONTEXT scope/description by @bigludo7 in Improve 403 INVALID_TOKEN_CONTEXT scope/description Commonalities#377
• Updated message field and description for Error 429 by @rartych in Updated message field and description for Error 429 Commonalities#390

Expected behavior

QoD APIs are aligned with the above changes.

• Apply the common artifacts for testing error scenarios for device and phoneNumber #404
• Add string patter to x-correlator scheme #405
• Check if Subscriptions and Notifications artifacts errors aligment -enum values- Commonalities#361 requires additional changes compared to Update error responses and test cases to comply with Commonalities 0.5.0 #391
  • Update: checked, both quality-on-demand and qod-provisioning look to be compliant with Commonalities r2.2
• Check if 429 error responses need to be updated according to Updated message field and description for Error 429 Commonalities#390 and Clarification on non-mandatory error statuses, 429 made non-madatory Commonalities#374
  • Update: Checked and there is a need to align. Hence adding a new sub-issue:
• Align 429 error reponses with CAMARA_common.yaml of Commonalities r2.2 #411

Alternative solution

Additional context

[hdamker]

done