Fixed Subscription API Detection

[hdamker]

What type of PR is this?

• correction

What this PR does / why we need it:

Refined the detection of the API type (Regular API, Implicit Subscriptions, Explicit Subscriptions.
Details below in "Additional documentation"

Which issue(s) this PR fixes:

Fixes #30

Special notes for reviewers:

Tested with:

• Prepare r3.1 DeviceLocation#360 in https://github.com/hdamker/ReleaseManagement/actions/runs/16252303084
• Prepare release r1.1 DeviceRoamingStatus#33 in https://github.com/hdamker/ReleaseManagement/actions/runs/16252102910
• Release Candidate r3.1 CarrierBillingCheckOut#232 in https://github.com/hdamker/ReleaseManagement/actions/runs/16252094064

Note: all API types identified correctly. For the scope naming issues for Explicit Subscription APIs opened #35

Changelog input

 release-note

Additional documentation

• Added API name parameter: Modified _detect_api_type() to accept an optional api_name parameter and use it to check if the API follows CAMARA naming conventions (ends with -subscriptions)
• Fixed schema detection logic: Replaced the broad check that flagged any schema with "subscription" in its name; now only considers it an event subscription schema if it contains a subscriptionId property
• Stored API name as instance variable: Added _current_api_name to store the API name when processing, allowing other validation methods to access it without passing it as a parameter
• Decision based on multiple factors: Changed from immediately returning EXPLICIT_SUBSCRIPTION when finding "subscription" in schema names to collecting evidence and making the decision based on both API naming convention and presence of event subscription properties

[rartych]

LGTM

[Kevsy]

LGTM