fix(geofencing-subscriptions): align with Commonalities r4.4

[hdamker]

What type of PR is this?

correction

What this PR does / why we need it:

Brings geofencing-subscriptions to Commonalities 0.9.0 (r4.4):

• Bumps x-camara-commonalities and re-syncs the additional-error-responses template.
• Replaces the deprecated Generic<status> responses and local copies with the r4.4 catalogue and CAMARA_event_common.yaml responses, following the r4.4 subscription template. Where the extra codes of a response cannot occur, the narrower catalogue response is used: BadRequest400 on the list operation and the notification callback, TooManyRequests429 on the callback.
• Renames CreateSubscriptionUnprocessableEntity422 (a deprecated common name in r4.4) to CreateGeofencingSubscriptionDevice422: the codes of the common CreateSubscriptionDevice422 plus the two GEOFENCING_SUBSCRIPTIONS.* codes.
• Keeps a local TooManyRequestsWithQuota429 on create, as no catalogue response declares both TOO_MANY_REQUESTS and QUOTA_EXCEEDED.
• Extends the common ConfigBase, references the common Sink, ErrorInfo and SubscriptionPermissionDenied403 directly, and removes unused or pass-through local aliases.
• Error examples reference the shared example pools; only the GEOFENCING_SUBSCRIPTIONS.* examples stay inline.
• Normalises the OAS pointers in the feature file to the #/ prefix.

Locally defined error responses drop from 10 to 2.

Which issue(s) this PR fixes:

Fixes #435

Special notes for reviewers:

• Two breaking changes (Design Guide §7.4, adding responses to existing operations), permitted because the API is at Initial status (0.y.z; last public version 0.5.0, 0.6.0 so far only shipped as rc):
  • create 400 references the common CreateSubscriptionBadRequest400, which adds OUT_OF_RANGE (reachable via range-constrained properties such as subscriptionMaxEvents and radius).
  • create 422 adds MULTIEVENT_COMBINATION_TEMPORARILY_NOT_SUPPORTED. Like the already declared MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED it cannot occur while types has maxItems: 1; declaring both now keeps a later relaxation of maxItems non-breaking.
• Dropping codes that cannot occur (OUT_OF_RANGE on the list and callback 400, QUOTA_EXCEEDED on the callback 429) affects no client.
• Pagination of the subscription list is not adopted: optional in r4.4, and breaking per §7.4.
• Examples that became $refs lose their local summary: — the pool examples carry description only.
• Remaining validation findings: P-027/S-211 in the other two specs (fix: align location-retrieval and location-verification with Commonalities r4.4 #436) and G-004/S-313, deferred in [geofencing-subscriptions] Deferred validation findings for r4.1 — G-004 scenario count #422. Test follow-ups: [geofencing-subscriptions] Test definitions: OUT_OF_RANGE coverage and multievent scenario vs maxItems: 1 #438.

Changelog input

fix(geofencing-subscriptions): align with Commonalities r4.4
BREAKING: createGeofencingSubscription declares two additional error codes, 400 OUT_OF_RANGE and 422 MULTIEVENT_COMBINATION_TEMPORARILY_NOT_SUPPORTED

Additional documentation

This section can be blank.

docs

[hdamker]

@camaraproject/device-location_codeowners

Updated the PR after an own review with two commits (ba2090e, c08a73d) and updated the description accordingly. Now again ready for review.

[bigludo7]

LGTM

[hdamker]

Merging so that I can sync #439 again with main.