docs: consolidate CQM API introduction structure

[albertoramosmonagas]

What type of PR is this?

Add one of the following kinds:

• cleanup
• documentation

What this PR does / why we need it:

Clean up the CQM API introduction document to make it more suitable for an external API consumer audience.

Key changes:

• remove duplicated sections, tables and legacy draft content;
• resolve and remove remaining Editor's Notes from the document body;
• consolidate the core CQM concepts into a single plain-language section;
• clarify the terminology around connectivity quality, connectivity performance characteristics and service-availability outcomes;
• separate scope and portfolio grouping from the API deep dives;
• reorder the API deep dives so discovery/support APIs are introduced first;
• simplify the live-event journey and avoid turning it into a prescriptive API selection guide;
• move GSMA use-case references to an appendix and replace the API applicability matrix with explanatory use-case references;
• clarify that dedicated-network-areas is treated as a preview service-area discovery capability;
• consolidate the comparative matrix, key takeaways, guardrails and source notes.

The resulting document keeps the focus on portfolio explanation rather than internal WG alignment, YAML details or CSP implementation guidance.

[albertoramosmonagas]

Adding this appendix to address the TSC feedback asking for at least some context on related CAMARA APIs outside the main Connectivity Quality Management scope.

The intent is not to expand the scope of this whitepaper or turn it into a full Communication Quality API comparison. The main body of the document remains focused on the CQM portfolio: qos-profiles, quality-on-demand, qos-provisioning, qos-booking, qos-booking-and-assignment, and the Dedicated Networks API family.

However, the CAMARA API overview also lists other APIs under the broader Communication Quality area, such as Application Profiles, Connectivity Insights, Predictive Connectivity Data, Session Insights, and Network Slice APIs. Since some readers may see those APIs next to the CQM APIs in CAMARA public material, it is useful to briefly clarify how they relate and why they are not covered in depth here.

This appendix should therefore be read as a scope-boundary clarification, not as a normative API selection guide or as an attempt to compare all Communication Quality APIs.

See this commit change to only see 26c7d3d the related changes

[tlohmar]

Yes, the request make sense.

However, we have not worked with the other APIs and may not reflect their intentions correctly. Maybe better to just list / link these APIs.
Do we know, whether there are more Connectivity Quality APIs coming with the Sync26 Meta Release?

[albertoramosmonagas]

I don't have a strong opinion on this. All I did was feed the AI ​​with the marketing descriptions that the groups had previously uploaded. So, if the source is truly good, I assume this is too? But I'm open to all kinds of suggestions and opinions at this point.