updating exposure and experience mgmt API spec to address issue #38 and #151

[maheshc01]

What type of PR is this?

Add one of the following kinds:

• bug
• correction
• enhancement/feature
• cleanup
• documentation
• subproject management
• tests

What this PR does / why we need it:

addresses #38 and #151 as well as fixes all linting errors

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[javierlozallu]

As was discussed in #229 and agreed at Edge Cloud meeting (21/05) documentation must be integrated in the yaml file following commonalities structure https://github.com/camaraproject/Commonalities/blob/main/documentation/API-DocumentationTemplate.md

[maheshc01]

@javierlozallu as discussed during the meeting , i have moved the edge discovery service yaml in its current form to the API proposals documents. This yaml has replaced existing/older MEC Experience and exposure mgmt API.
Next steps would be to break down the functionality of edge discovery service api into 3 different yaml

1. Application profiles API
2. Application end point registration API
3. Discovery API (2 discovery APIs- 1 for optimal edge cloud discovery and other for optimal application end point discovery)

Request to approve and merge this PR.

[linux-foundation-easycla]

• ✅ login: maheshc01 / name: Mahesh (f0b64ec, 5f0d3ab, a29882a, 8ca9b8b, b437b2d, 4b850aa, 87417b5, 47de348, db73369, 04209d5, 52bcc40)
• ❌ The email address for the commit (59e22a8, 7865eca, 1f560e1, f9dea79, bee38b2, 3e09fb8, 7915cda, d128801, 75fc3cd, 7c1755c, 54edc86, 6e3393b, f9a0baf, 14b701b, 786d8ff) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.