test(geofencing-subscriptions): align test definitions with the API definition

[hdamker]

What type of PR is this?

tests

What this PR does / why we need it:

Aligns the geofencing-subscriptions test definitions with the API definition after the Commonalities r4.4 alignment, and splits them per operation:

• Adds @geofencing_subscriptions_400.9_out_of_range, a scenario outline for 400 OUT_OF_RANGE on createGeofencingSubscription (subscriptionMaxEvents below and above its range, radius below its minimum, latitude above 90).
• Marks @geofencing_subscriptions_422.3_create_with_unsupported_multiple_event_type as not applicable while types has maxItems: 1, keeping it for a future multi-event version.
• Splits geofencing-subscriptions.feature into one file per operation, named geofencing-subscriptions-<operationId>.feature as recommended by the API Testing Guidelines. Scenarios are moved unchanged; notification scenarios go with create, the deletion-ended notification with delete.

File	Scenarios
...-createGeofencingSubscription.feature	37
...-retrieveGeofencingSubscriptionList.feature	5
...-retrieveGeofencingSubscription.feature	6
...-deleteGeofencingSubscription.feature	7

Which issue(s) this PR fixes:

Fixes #438
Fixes #422

Special notes for reviewers:

• Based on fix(geofencing-subscriptions): align with Commonalities r4.4 #437, which adds OUT_OF_RANGE to the create 400; draft until fix(geofencing-subscriptions): align with Commonalities r4.4 #437 is merged, then rebased on main.
• The only scenario spanning two operations, @geofencing_subscriptions_403_subscription_mismatch, becomes 403.1_retrieve_subscription_mismatch and 403.2_delete_subscription_mismatch, one per file.
• The split clears G-004 (53/50). The remaining S-313 hint is on the free-form subscription id (same shape as the common SubscriptionId) and needs no fix.
• 400.1 stays as in the Commonalities test template; out-of-range values are covered by 400.9.

Changelog input

test(geofencing-subscriptions): add OUT_OF_RANGE test scenario and split test definitions into one feature file per operation

Additional documentation

This section can be blank.

docs