Generate Key Vault libraries from tsp

[RickWinter]

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

• Cmake should have 2 parts the global functinality (download/generate in global cmake, and a private part in the folder relating to which TSP )

• While we plan to not have any test changes and to preserve the existing public API surface we don't know if theat will be the case.

• The first set take longer as they are the POC for this whole thing for C++.

• Subject to change especially due to the tests steps and this being the first time we do this. I don't know what will crop up out of this exercise.

• These are guestimates take with a grain of salt.

Secrets

• Cmake download TSP | 1 day
• CMAKE Integrate TSP generation | 2 days
• Test related Updates | 3 days (should not be the case)
• Customizations/TSP overrides | 5 days
• Update docs | 1 day
• Update samples | 1 day

Keys

• Cmake download TSP | 0.5 day
• CMAKE Integrate TSP generation | 1 days
• Test related Updates | 3 days (should not be the case)
• Customizations/TSP overrides | 5 days
• Update docs | 1 day
• Update samples | 1 day

Certs

• Cmake download TSP) | 0.5 day
• CMAKE Integrate TSP generation | 1 days
• Test related Updates | 3 days (should not be the case)
• Customizations/TSP overrides | 5 days
• Update docs | 1 day
• Update samples | 1 day

Admin

• Cmake download TSP | 1 day
• CMAKE Integrate TSP generation | 2 days
• Test related Updates | 3 days (should not be the case)
• Customizations/TSP overrides | 5 days
• Update docs | 1 day
• Update samples | 1 day

FOLLOWUP

• Download the typspec-cpp emitter from npmjs.org | 1 day