Sync Commonalities to r4.4 (0.9.0)

[DLondonoD]

What type of PR is this?

• enhancement/feature

What this PR does / why we need it:

Bumps this API's Commonalities target from r4.3 (0.8.0) to r4.4 (0.9.0) and adopts the resulting Design Guide changes:

• Resynced code/common/CAMARA_common.yaml, CAMARA_event_common.yaml and info-description-templates.yaml to their r4.4 content, updating .sync-manifest.yaml with the corresponding blob hashes, and bumped info.x-camara-commonalities to 0.9.0.
• Updated the mandatory "Additional CAMARA error responses" info.description text to r4.4's wording (points to x-camara-commonalities/changelog/release metadata instead of the removed "API Readiness Checklist" document reference).
• Replaced every $ref to the deprecated Generic400/401/403/404 responses with the new named catalogue from CAMARA_common.yaml (BadRequest400, Unauthenticated401, PermissionDenied403, NotFound404), and removed this API's local Generic400/403/404 overrides, which existed only to work around a P-040 bundling name collision that no longer applies.
• Migrated locally-defined 409 responses (ALREADY_EXISTS/INCOMPATIBLE_STATE) to the CAMARA_common.yaml Track-2 template (ErrorInfo allOf'd with a local status/code enum restriction), matching the r4.4 Design Guide's required pattern for locally-defined error responses.
• SubscriptionRequest.sink now $refs the shared Sink schema in CAMARA_event_common.yaml instead of duplicating its string/format/pattern/maxLength definition locally.
• SinkCredential now allOf's the common AccessTokenCredential and locally restricts credentialType to ACCESSTOKEN only (PRIVATE_KEY_JWT, newly supported by Commonalities r4.4, is intentionally not offered by this API); the local AccessTokenCredential schema was removed as it's no longer needed.
• Added the new 422 EVENT_NOTIFICATIONS_NOT_SUPPORTED response (components/responses/EventNotificationsNotSupported422) to both createAppInstance and createAppDeployment, documenting that providing subscriptionRequest.sink when the Edge Cloud Platform cannot deliver notifications results in this error without creating the resource.
• Added additionalProperties: false to every request body schema (and inline request body) with no composition at its own top level, per the r4.4 Design Guide's Appendix B strictness guidance.
• Reformatted enum descriptions with per-value meaning into markdown bullet lists, per Appendix B.3.

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Not addressed in this PR (tracked separately):

• Local duplication of SinkCredential/AccessTokenCredential/sink/SubscriptionConfig against the r4.4 CAMARA_event_common.yaml equivalents (Sink, SinkCredential w/ PRIVATE_KEY_JWT, ConfigBase) is only partially resolved here.
• Echoing sink back in AppInstanceInfo/AppDeploymentInfo on success, as newly recommended by the Guide, is a separate schema change and is not part of this PR.
• AppManifest is deliberately excluded from the additionalProperties: false change: it's allOf'd into AppManifestInfo (adding the appId property), and restricting it directly would make that allOf combination invalid under standard JSON Schema semantics.

Changelog input

release-note
Sync Commonalities to r4.4 (0.9.0): adopt the shared named error response catalogue, Track-2 pattern for local error responses, shared Sink/AccessTokenCredential schemas, the new 422 EVENT_NOTIFICATIONS_NOT_SUPPORTED response, additionalProperties: false on request bodies, and bullet-list enum descriptions.

Additional documentation

docs

[Kevsy]

LGTM