Fixed for complete native support for remaining azure-resourcemanager libs

[v-hongli1]

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

API changes are not detected in this pull request.

[weidongxu-microsoft]

The json file depends on the Java files generated via codegen.

Are you sure there is not even a single new file added, or old file removed/renamed?

[v-hongli1]

@weidongxu-microsoft
The situation as adding new files, or deleting/renaming old files not found in the submitted section.

[weidongxu-microsoft]

@weidongxu-microsoft The situation as adding new files, or deleting/renaming old files not found in the submitted section.

No. I mean is there any such case when you "generate" the code (but not included in submit).

[v-hongli1]

@weidongxu-microsoft The situation as adding new files, or deleting/renaming old files not found in the submitted section.

No. I mean is there any such case when you "generate" the code (but not included in submit).

I have confirmed the generated codes one by one, and no such situation occurs except for monitor.