migrate azure-analytics-defender-easm to azure-json

[weidongxu-microsoft]

link #40614

Another attempt on easm, as service have no response on task #39862

spec target Azure/azure-rest-api-specs#29839
I've cleaned src/main before regen.

Service removed subscriptionId, resourceGroupName, workspaceName parameters from their typespec server endpoint. Now the endpoint contains all of them, as e.g. https://<host>/subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/workspaces/<workspaceName>/. This is the cause of change in client builder.

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

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

com.azure:azure-analytics-defender-easm

[azure-sdk]

API change check

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

com.azure:azure-analytics-defender-easm

[weidongxu-microsoft]

/azp run java - easm - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).