Switch Key Vault library to be based on TypeSpec

[RickWinter]

Goal here is to generate the libraries from TSPs while we want to maintain surface area.

There are two primary objectives from this work:

1. Add support in dataplane for generating libraries using the TypeSpec-Go generator
2. Convert KeyVault library to generate from TypeSpec

For repo infrastructure we need to do the following:

• [ ] Add Support to go generate for TypeSpec

For each library (Secrets / Keys / Certs / Admin) we will need to do the following:

• [ ] go build TSP generation | 2 days
• [ ] Add language customizations to the TSP files in rest-api-specs repo | 5 days

[chlowell]

This is the high-level process for each library:

• add language-specific configuration to the library's tspconfig.yaml in the azure-rest-api-specs repo. See these PRs:
  • https://github.com/Azure/azure-rest-api-specs/pull/30239
  • https://github.com/Azure/azure-rest-api-specs/pull/28708
  • https://github.com/Azure/azure-rest-api-specs/pull/29248
  • https://github.com/Azure/azure-rest-api-specs/pull/29249
• check tsp-client setup for SDK repo (docs)
• add tsp-location.yaml for the library (docs, example)
• generate code with tsp-client
• add customization to client.tsp (example)

[gracewilcox]

CURRENT PROGRESS:

• [ ] admin
  • [ ] generate BLOCKED-CANT GENERATE
  • [ ] add modifications
  • [ ] in PR
  • [ ] merged
• [ ] certificates
  • [x] generate
  • [x] add modifications
  • [x] in PR
  • [ ] merged
• [ ] keys
  • [x] generate
  • [x] add modifications BLOCKED- BUG
  • [x] in PR
  • [ ] merged
• [ ] secrets
  • [x] generate
  • [x] add modifications
  • [x] in PR
  • [ ] merged