Remove 12 unused schema components flagged by S-211 (location-retrieval, geofencing-subscriptions)

[hdamker]

Problem description

CAMARA Validation flags 12 unused schema components (S-211) across two API specs. These are local pass-through aliases (SchemaName: {$ref: '../common/CAMARA_common.yaml#/components/schemas/SchemaName'}) left over from the Commonalities r4.3 sync (#408) that nothing in either spec actually references — all real use sites point directly at CAMARA_common.yaml, not at the local alias.

location-retrieval.yaml:

• Device (line 251)
• AreaType (line 260)
• Circle (line 263)
• Polygon (line 266)
• PointList (line 269)
• Point (line 272)
• Latitude (line 275)
• Longitude (line 278)

geofencing-subscriptions.yaml:

• PhoneNumber (line 602)
• NetworkAccessIdentifier (line 605)
• Port (line 608)
• DeviceIpv6Address (line 611)

Expected behavior

Remove these 12 unused local alias schemas. Same cleanup already done for the other unused aliases in this file by #417 and #420 — this list is what those two PRs missed.

Additional context

Found while reviewing #431. S-211 was hint-level (not blocking) until camaraproject/tooling#378 promoted it to warn, so these went unnoticed until now.

#431 also surfaces two other r4.4-alignment warnings, tracked separately: additional-error-responses template drift (P-027) in all three specs, and the geofencing-subscriptions scenario count exceeding 50 (G-004).

[hdamker]

Superseded by the two Commonalities r4.4 alignment issues, which each absorb the half of this list that falls in their spec:

• Align location-retrieval and location-verification with Commonalities r4.4 #434 — location-retrieval and location-verification: Device (line 251), AreaType (260), Circle (263), Polygon (266), PointList (269), Point (272), Latitude (275), Longitude (278) in location-retrieval.yaml. location-verification.yaml has no S-211 findings.
• Align geofencing-subscriptions with Commonalities r4.4 #435 — geofencing-subscriptions: PhoneNumber (line 602), NetworkAccessIdentifier (605), Port (608), DeviceIpv6Address (611).

Both issues touch the same two files for the r4.4 alignment anyway, so folding these deletions in avoids a separate PR that the other two would have to wait for and rebase onto. Nothing is dropped — all 12 components are still listed, per file, with the same rationale.

Closing as superseded.