[tsp init] Azure project should be initiated with a tspconfig file with options for client code generation

[josefree]

Clear and concise description of the problem

suggest to improve the TypeSpec project templates for Azure. New Azure service can start from "tsp init https://aka.ms/typespec/azure-init" to scaffolding their TypeSpec project. Currently, after initializing, the tspconfig.yaml has only autorest configuration. The expectation is that it should be initialized with typespec- configurations too, referring to azure-rest-api-specs/specification/contosowidgetmanager/Contoso.Management/tspconfig.yaml at main · Azure/azure-rest-api-specs ('contoso' should be replaced by the namespace specified by user in responding to the question "Please provide ARM Resource Provider Name in Pascal case". see screenshot below.).

Checklist

• [x] Follow our Code of Conduct
• [x] Check that this issue is about the Azure libraries for typespec. For feature request in the typespec language or core libraries file it in the TypeSpec repo
• [x] Read the docs.
• [x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[maririos]

I believe this is the same as issue I recently opened: https://github.com/Azure/azure-sdk-tools/issues/9382