Edge discovery APIs enhancements

[kohlian18]

What type of PR is this?

• enhancement/feature
• cleanup
• Documentation

What this PR does / why we need it:

This segregates and simplifies edge cloud zone and application endpoint discovery APIs:

• GET edge cloud regions API to fetch edge cloud region id and name required for discovery APIs.
• POST method containing standardised device information schema along with application profile id for edge cloud zone discovery.
• POST method along with device information with application endpoint ids and edge cloud regions for application endpoint discovery.
• added information for access and authorisation token

[gunjald]

I suppose this intent "discover optimal edge cloud zones for deployed applications" is valid for the end users which would connect with the edge applications instances. In that case we need to possibly indicate the different type of users who may consume these APIs.

[gunjald]

It is bit confusing when it says the users can use this API to enhance connectivity and performance by selecting suitable edge cloud zone and application endpoints. In my view the app providers may need to use this API to deploy applications while the end users may use it just to discover application endpoints to connect with.
So in terms of the usage it would be good to describe the scenario where the given intents are to be used by the intended users as per the goals of the API. Thoughts?

[kohlian18]

resolved

[gunjald]

As per the use cases described here it seems to propose two category of users that is app developers and client applications. If this is correct how does API assumes the authorization for these users interactions with API?