Edge device creation, configuration, and device bundles

[c-ryan-k]

Adds az iot edge devices create command that allows users to create and configure multiple edge device scenarios (and associated device configuration settings) using a configuration file (YAML or JSON) or inline device arguments.

The command performs the following actions after processing input:

• Verify parent-child relationships between devices
• [Optional] Delete all devices on the hub before creation
• Create all new device-identities
• Assign parent scopes to devices
• Set deployments / modules on devices
• Creates device config bundle (.tgz) that contains:
  • Device certificates
  • Root CA certificate (self-signed or imported)
  • Install script and readme

---

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).

[c-ryan-k]

First round of tests - have one final one (hopefully) coming that updates unit and integration tests so I'll have another run starting shortly.

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

[c-ryan-k]

Ok, one last full pipeline run to go once the PR pipeline passes, but here's some local testing evidence:

[c-ryan-k]

Looks like tests were mostly successful, save some of our recent recurring issues. I'm good with this.