Migrate trafficmanager TypeSpec

[v-hongli1]

This PR migrates your latest version (identified by the tag in your readme.md) of swagger to TypeSpec. We already tried our best to make sure the TypeSpec represents same as previous swagger. Since we lack the business knowledge, please validate this PR again to make sure it's functional equivalent as before. The local validation step is at Getting started | TypeSpec Azure

Besides, TypeSpec encourages to follow ARM guidelines. Therefore, some representations in your previous swagger will be fixed to follow these guidelines. When you see differences in your local validation, please keep this note in mind. Here is the list you need to pay attention:

Please reach out to TypeSpec Discussions Channel if there is any help needed.

[github-actions]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ This PR has at least one breaking change (label: BreakingChangeReviewRequired).
  To unblock this PR, follow the process at aka.ms/brch.
• ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.

Comment generated by summarize-checks workflow run.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language	API Review for Package
Swagger	Microsoft.Network
TypeSpec	Microsoft.Network
Go	sdk/resourcemanager/trafficmanager/armtrafficmanager
JavaScript	@azure/arm-trafficmanager

[v-hongli1]

@pshao25
The commit#c8d02e6 and commit#d3c0f2e are try to add the ResourceNameParameter to the model. You can view the results in CI. I recommend not adding the ResourceNameParameter to avoid Swagger ModelValidation exceptions.

[pshao25]

@pshao25 The commit#c8d02e6 and commit#d3c0f2e are try to add the ResourceNameParameter to the model. You can view the results in CI. I recommend not adding the ResourceNameParameter to avoid Swagger ModelValidation exceptions.

Don't recommend anything before you get into the root cause of the pipeline failures. In your case, the pipeline failed because its original resource's type property is not readonly, while if we extend from the resource from our library, it is readonly.