Consolidate relevant API & SDK release data in engagement experience database

**Requirement:** The relevant API & SDK release data needs to be aggregated, stored, and maintained in one database solution. Today there is data in GitHub, ADO, Release plan dataverse, APIView, etc.

For example, the inventory dashboard data is not easily accessible from GitHub and it does not contain the Service Tree ID so that we can leverage and use the data in the release planner app. If the data were accessible, then we could query the data to determine if the Service for a new product onboarding to the SDK System has existing data or management plane REST APIs and SDKs. Today the answer to this question during onboarding is self-attested, which is prone to human error and data integrity issues.

**Data requests from SDK release team**

- [ ] Determine which data fields are relevant and overall state (where is data stored today, is accessible, etc).
- [ ] Confirm and validate data requirements with the SDK release stakeholders.
- [ ] Identify current gaps and provide requirements to resolve. For example, there is not currently a programmatic way to obtain most of the data requested by SDK release stakeholders for driving future improvement. There will need to be process improvement to automate obtaining accurate and complete data for these fields.