fix: warnings following rc PR validation

[Kevsy]

Problem description

The automated review of the release-candidate PR indicated validation errors to be fixed.

Expected behavior

Fix the following errors and warnings as per the directives:

Errors (3)
[S-209] OpenAPI document fails OAS 3.x schema — 3 hits

• code/API_definitions/simple-edge-discovery.yaml:336:13 — [S-209] Property "name" is not expected to be here.
• code/API_definitions/simple-edge-discovery.yaml:337:11 — [S-209] Property "in" is not expected to be here.
• code/API_definitions/simple-edge-discovery.yaml:339:14 — [S-209] Property "schema" is not expected to be here.

Warnings (2)

• code/API_definitions/simple-edge-discovery.yaml:335:18 — [S-015] x-correlator should be PascalCase (UpperCamelCase)
• code/API_definitions/simple-edge-discovery.yaml:335:18 — [S-016] Missing 'type' at components.schemas.x-correlator

Note, the remaining hints in the review have previously been checked and can be ignored.

[Kevsy]

Errors:
These are caused by me using $ref to the common schema on every instance of x-correlator in the document. The release PR imports these and includes them inline in the new YAML. This results in unexpected schema objects appearing where they should not: the fix is to simply $ref the common schema definition once so it is imported into the YAML, and then all the other $refs point to the newly-include local definition.

Warnings:

1. x-correlator is correct. As an HTTP header, the API Design Guide notes that it is case-insenstive and it is spelled as x-correlator throughout the guide.

[hdamker]

I looked more closely at what happened in the Release Review PR validation.

The errors were not caused by x-correlator being lowercase as a header name. They came from object-kind mixing before the release snapshot was bundled. In main, the API definition referenced ../common/CAMARA_common.yaml#/components/parameters/x-correlator from inside schema: fields. That Commonalities object is a Parameter Object, so when the release snapshot bundled the external references it effectively produced a schema entry containing parameter fields such as name, in, and schema. That is why the Release Review PR reported S-209 errors at components.schemas.x-correlator.name, .in, and .schema, plus the related schema-name/type warnings.

Commonalities already has the three separate objects we need:

• components/parameters/x-correlator — Parameter Object, includes name: x-correlator and in: header
• components/headers/x-correlator — Header Object, for response headers
• components/schemas/XCorrelator — Schema Object, used inside those parameter/header definitions

So the fix is to reference the Commonalities object matching the OpenAPI location, rather than creating or importing a local mixed definition. PR #185 does that from current main: operation parameters reference the Commonalities Parameter Object, response headers reference the Commonalities Header Object, and the local duplicate components.headers.x-correlator definition is removed. Its validation is green, and the bundled artifact keeps the parameter, header, and schema objects separate.