[Key Vault] Target multiple API versions with tests (certificates)

[mccoyp]

Part of #12376.

This uses the parameterized package to parameterize Key Vault tests, targeting every API version when possible. This produces a recorded test for each API version per test -- for example, test_crud_operations -> test_crud_operations_2016_10_1, test_crud_operations_7_0, and test_crud_operations_7_1.

This adds recordings for each of these tests, so that full API version coverage can be achieved in playback. For live tests though, only the default API version is used for the majority of tests (to lighten the load of live testing).

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

[mccoyp]

/check-enforcer reset

[mccoyp]

/azp run python - keyvault - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).