Vulnerable uuid dependency via deprecated @azure/ms-rest-js

## Summary

`azure-iothub` currently depends on vulnerable versions of `uuid` through its dependency on `@azure/ms-rest-js`.

Running `npm audit` reports the following vulnerability:

```
# npm audit report

uuid <11.1.1
Severity: moderate
uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided - https://github.com/advisories/GHSA-w5hq-g745-h8pq
fix available via `npm audit fix --force`
Will install azure-iothub@1.16.5, which is a breaking change
node_modules/uuid
@azure/ms-rest-js *
Depends on vulnerable versions of uuid
node_modules/@azure/ms-rest-js
azure-iothub 1.0.0-preview.3 - 1.1.16 || >=1.13.0-pnp-rc.0
Depends on vulnerable versions of @azure/ms-rest-js
Depends on vulnerable versions of uuid
node_modules/azure-iothub
```

## Additional context

It should also be noted that `@azure/ms-rest-js` has been deprecated in favor of the newer Azure SDK packages maintained in the Azure SDK for JavaScript repository. The deprecated repository is marked as read-only since Jun 11, 2026

Since `azure-iothub` still depends on this deprecated package, consumers are left with an unresolved **moderate** vulnerability, and downgrading to 1.15.5 doesn't seem to fix the issue.

## Expected behavior

Update the dependency chain to eliminate the vulnerable transitive dependency on uuid (GHSA-w5hq-g745-h8pq). This may require updating or replacing the deprecated @azure/ms-rest-js dependency.

## Impact

Projects using `azure-iothub` receive security audit warnings for a transitive dependency that they cannot remediate directly, resulting in failed security scans and CI pipelines.

Start by inspecting azure-iothub's dependency declarations and the installed dependency tree, then run npm audit to confirm how @azure/ms-rest-js brings in uuid. Done means the vulnerable uuid chain is eliminated without breaking azure-iothub consumers, with the audit output and package behavior checked afterward.

Written by the indexing model from the issue text.