Deprecate previous sdk generation tooling

[maririos]

With tsp-client, documentation and scripts for additional TypeSpec tooling is no longer necessary. To make sure our users don't get confused, we should remove these tooling.

• https://github.com/Azure/azure-sdk-tools/blob/main/doc/common/TypeSpec-Project-Scripts.md
• https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/scripts/TypeSpec-Project-Generate.ps1
• https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/scripts/TypeSpec-Project-Sync.ps1
• https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/scripts/TypeSpec-Project-Process.ps1

CADL tooling?

• https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/scripts/Cadl-Project-Sync.ps1
• https://github.com/Azure/azure-sdk-tools/blob/main/eng/common/scripts/Cadl-Project-Generate.ps1

Spec repo references:

• Documentation that needs to be updated to use tsp-client
• Also, issue filed by a user: TypeSpec-Project-Process.ps1 no longer exists but referenced in docs and code azure-rest-api-specs#30544

Language repos references:

• .NET:
  • DPG documentation (seems out of date?)
  • Clean up .NET automation scripts #9422
• Java:
  • Update-java-GeneratedSdks should not use the Typespec-project scripts #9421
• Python:
  • TypeSpec refresh SDK What is this?
• JS
  • Documentation
  • Update-javascript-GeneratedSdks should not use Typespec-project scripts #9420
• Go
  • Used for test data?

[maririos]

Python:
TypeSpec refresh SDK What is this?

Email sent to Python team to understand what this is

[maririos]

Go
Used for test data?

Message sent to previous Go sdk generation owner to understand more