[IoT] Increase SDK and API version

[vilit1]

Related command

az iot hub
az iot hub create
az iot hub route test
az iot dps linked-hub create

Description
Increase the API version to 2022-04-30-preview and pin the min SDK to azure-mgmt-iothub==2.3.0. This will enable customers to modify the control plane of hubs that have features from the 2022-04-30-preview API, specifically the Cosmos DB endpoints.

The Cosmos DB Endpoint feature will be released in the azure iot extension.

There is also some small fixes:

1. the fileupload_storage_container_uri parameter is no longer used and is removed in this pr. This will remove the warning message below that occurs during hub creation.
   
2. the app_properties and system_properties for hub routes will now be converted to a dictionary (and thus make the routes test work)
3. the dps linked hub will now have an error message about location - so that if a hub is provided in a different subscription, then the user will be prompted to give the location. This will fix the customer confusion as seen in this issue: az iot dps linked-hub create hub and DPS on different subscriptions broken!? #22257
4. Add preview to device streams as part of Mark DeviceStreams commands as Preview #24554
5. Fix a networking test in which az iot device-update was renamed to az iot du
6. Add no wait to iot hub create and delete

Testing Guide

Regenerated all affected iot commands. Also added a test to route test (that would have failed in the older version)

History Notes

[IoT] Fix #22257: az iot dps linked-hub create: Improve error handling for linked hubs
[IoT] az iot hub create/delete: Add --no-wait parameter to support no wait operation

---

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

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[yonzhan]

IoT Hub

[zhoxing-ms]

[IoT Hub] Increase min SDK and API version
[IoT Hub] Remove warning during Hub creation and fix routes test
[IoT Dps] Improve error handling for linked hubs

We usually only write the changes that can be perceived by users and affect users' business in the history notes, so I personally think the first and second points can be deleted.
Could you describe the third point in more detail?

[vilit1]

[IoT Hub] Increase min SDK and API version
[IoT Hub] Remove warning during Hub creation and fix routes test
[IoT Dps] Improve error handling for linked hubs

We usually only write the changes that can be perceived by users and affect users' business in the history notes, so I personally think the first and second points can be deleted. Could you describe the third point in more detail?

3. the dps linked hub will now have an error message about location - so that if a hub is provided in a different subscription, then the user will be prompted to give the location. This will fix the customer confusion as seen in this issue: az iot dps linked-hub create hub and DPS on different subscriptions broken!? #22257

The second point will affect users too:

1. the fileupload_storage_container_uri parameter is no longer used and is removed in this pr. This will remove the warning message below that occurs during hub creation.
   
2. the app_properties and system_properties for hub routes will now be converted to a dictionary (and thus make the routes test work)

[zhoxing-ms]

The second point will affect users too

In fact, the warning log has no real impact on the user's business, so we usually do not write the changes of warning log into the history notes.

[IoT] Fix #22257: az iot dps linked-hub create: Improve error handling for linked hubs

This is my updated history note, please see if it meets your expectations