Combining EDS API with AED API

[javierlozallu]

Problem description
In EDS API GET /application-endpoints (at first glance and because of the name, it might overlap with AED API) and GET /mecplatforms (at first glance it might overlap with SED API or GET /edge-cloud-zones of EAM API).

GET /application-endpoints ESD API vs GET /app-endpoints AED API:

GET /application-endpoints ESD API: Returns a list of optimal Application Endpoints that client devices can connect to. You can search based on Application Profile, Region, Suscriber Density or UEIdentity.

This method is very interesting and covers part of intent 21, which is outside the scope of the MVP proposal, but was considered for the improvement phase.

Expected behavior

GET /app-endpoints AED API: Returns the closest endpoint of the App Instance for an specific UE. Based on UEIdentity and AppID
This functionality can be merged to improve Application Endpoint Discovery capability, allowing endpoint discovery based on App Profile, Region, Subscriber Density, UEIdentity and AppId.