Adding Device Provisioning Service in Azure IoT SDK

[Ellerbach]

Description

Adding Device Provisioning Service in Azure IoT SDK

Motivation and Context

• Adding Device Provisioning Service in Azure IoT SDK
• Improving current SDK for closing and disposing properly the mqqt client
• Documentation added in the main README.md
• Samples to be added once PR approved and merged

How Has This Been Tested?

Thru real device on an ESP32 with the code provided in th README.md file

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (work on Unit Tests, has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[josesimoes]

Perfect! Clean and simple as we like it. 👍👏