Parallelize DPS tests

[vilit1]

Somehow parallelize DPS tests - so that each thread gets a file.

The enrollment (and group) tests no longer erase the previous enrollments. Instead, they focus on if the added enrollment is there (regardless of whatever was added before it). Hubs generated by dps tests are no longer tagged - instead the dps now has the tag to say which hub it is (or at least was) associated with. Doing pipeline runs with iot hub to make sure we are not hitting any limit (hub or dps max num limit) some refactoring of certificate tests for parallization small change to wording of an error

The tests use a single hub:

• it is created before the dps integration tests in the pipeline. the config is changed to use that hub.
• the same hub will be used within a job (ex: dps tests for python 3.8 will share one hub, while dps tests for python 3.9 will share a separate hub)
• the hub name is test-dps-hub-pyxxxxx with the x's being a random number determined by $RANDOM.
• If a hub is already specified in the pipeline variables, that config value will remain the same and the pipeline will run with the specified hub.
• the created hub is deleted at the end.

First success: https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6015&view=results

current run: https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6053&view=results

---

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Thank you for contributing to the IoT extension!

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

Intent for Production

• [ ] It is expected that pull requests made to default or core branches such as dev or main are of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.

Basic expectations

• [ ] If introducing new functionality or modified behavior, are they backed by unit and/or integration tests?
• [ ] In the same context as above are command names and their parameter definitions accurate? Do help docs have sufficient content?
• [ ] Have all the relevant unit and integration tests pass? i.e. pytest <project root> -vv. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set.
• [ ] Have linter checks passed using the .pylintrc and .flake8 rules? Look at the CI scripts for example usage.
• [ ] Have extraneous print or debug statements, commented out code-blocks or code-statements (if any) been removed from the surface area of changes?
• [ ] Have you made an entry in HISTORY.rst which concisely explains your user-facing feature or change?

Azure IoT CLI maintainers reserve the right to enforce any of the outlined expectations.

A PR is considered ready for review when all basic expectations have been met (or do not apply).

[vilit1]

https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6066&view=results

[vilit1]

newest run: https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6071&view=results

hub is not defined for dps tests

[vilit1]

most recent run https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6098&view=results

[digimaun]

Have we tested against the nightly pipeline (which includes Windows MSI) as well?

[vilit1]

Have we tested against the nightly pipeline (which includes Windows MSI) as well?

https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6103&view=results

[vilit1]

run with an exception (as in this should fail) https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6105&view=results

[vilit1]

https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6115&view=logs&j=3ae2c7c4-5ec4-555e-d2bf-ad8987168812&t=1a02f018-e3e0-530d-ac6f-9f24b5e03c14

[vilit1]

with the updated if https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6127&view=results

merge https://dev.azure.com/azureiotdevxp/aziotcli/_build/results?buildId=6129&view=results