Expose supported api-versions for each service

We need to communicate to our customers which service **data plane** api-versions each library supports, so they can determine if they can use the new SDKs for their given instance of a service. For example, Cloud1 has KeyVault api-version 6.0 deployed, but the minimum supported value is 7.0 by the new SDKs. That customer would therefore need to use the previous SDKs.

These values are currently embedded within each SDK, but not exposed in a clean way to our customers.

The requirements are:
1. The service api-version supported values need to be easily managed by each service and SDK team.
1. The service api-version supported values need to be display in each service README.
1. The service api-version supported values need to be displayed with Docs core and any reference documentation.
1. The service api-version supported values need to be easily integrated into other software, such as the Azure global parity dashboard. Do not embed these values within markdown which will require integrators to parse markdown to retrieve the values. Provide the values in a format that is easily downloadable, such as a data file in the azure-sdk repo.
1. The service api-version supported values need to be surfaced on the https://aka.ms/azsdk/releases package list, so a customer can easily find all of these values without having to go to each repo individually.