Fix/use common schemas

[jimfengjinhua]

What type of PR is this?

Add one of the following kinds:

• enhancement/feature
• cleanup

What this PR does / why we need it:

To replace local common data type definitions with direct $ref to CAMARA_common.yaml. Remove all local definitions of XCorrelator, ErrorInfo, Device, Area, Point, and x-correlator header/parameter that duplicate CAMARA_common.yaml schemas. All references point directly to ../common/CAMARA_common.yaml.

Note: The dedicated-network-areas.yaml is now using the common data type Area, which consequently introduced an API contract change for Circle.radius:

	Type	Maximum
Original (local)	integer	200000
New (common Area)	number	none

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Changelog input

Replacing local common data type definitions with direct $ref to CAMARA_common.yaml. Remove all unused local definitions.
In dedicated-network-areas.yaml, Circle.radius has been changed from type integer (with maximum as 200000) to type number (without max limitation).

Additional documentation:

[hdamker]

@jimfengjinhua I removed @camaraproject/release-management_reviewers from the reviewer list as this is not a Release Review PR and volunteered myself to review.

[hdamker]

The changes are looking good, one point which need an explicit documentation within the PR description (and later in CHANGELOG):

dedicated-network-areas.yaml:181 now points service-area request/response shapes at common Area, but the removed local Circle.radius contract was integer with maximum: 200000; common Circle.radius is number with no max. That is a real API contract change for an RC API, not just de-duplication.

[jimfengjinhua]

The changes are looking good, one point which need an explicit documentation within the PR description (and later in CHANGELOG):

dedicated-network-areas.yaml:181 now points service-area request/response shapes at common Area, but the removed local Circle.radius contract was integer with maximum: 200000; common Circle.radius is number with no max. That is a real API contract change for an RC API, not just de-duplication.

@hdamker thanks for your prompt review and comment. I have updated PR with the API contract change explicitly described, as well as in 'Changelog input' accordingly

[tlohmar]

Looks good.

[tlohmar]

Looks now ok