Separate of dedicated-networks-areas API into its own repository

[tlohmar]

Problem description

One finding of the CQM API Alignment Breakout session is that more APIs have the need for allowing discovery of network service areas, where a certain connectivity quality can be supported. Using trial-and-error type of discovery may give a negative experience.
Based on the decision in the Connectivity Quality Management Sub Project community (latest one in https://lf-camaraproject.atlassian.net/wiki/x/AQDcMQ) on the findings, the Sub Project would like to separate the dedicated-network-areas API out of the current DedicatedNetworks repository into its own repository:

• Repository Name: NetworkServiceAreas
  API Name: service-areas

The DedicatedNetworks repository would retain the dedicated-network, the dedicated-network-accesses and the dedicated-network-profiles APIs which are depending on each other.
The initial contribution to the new repository will be for the Sync26 release.

Initial Codeowners: @hubertp-ericsson, @eric-murray, @Masa8106, @jlurien
Initial Maintainers: @hubertp-ericsson, @eric-murray, @Masa8106, @jlurien

Expected action

• Review and comment (if needed) on the proposed API name and the proposed list of codeowners and the proposed list of maintainers
• Track the creation of the new Service Areas repository here.
• Once the new repository exists, start migrating the dedicated-network-areas API into the new service-areas API.

Additional context