mgmt, iothub, add live tests

[v-hongli1]

relate to #35316

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.

[v-hongli1]

/azp run prepare-pipelines

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[v-hongli1]

/azp run java - iothub - mgmt - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[weidongxu-microsoft]

Could you locally regen iothub with a stable api-version (don't commit, don't check-in, we just need the code of a working api-version to run test), and test locally that your live test passes?

api-version problem raised in https://github.com/Azure/sdk-release-request/issues/3974, but we need to make sure your live tests works on at least one api-version (where backend is good).

[weidongxu-microsoft]

LGTM.

Please make sure your current test still pass the working api-version locally, before merge.