[Doc] The Az.storage dependency lacks documentation.

### Description

https://www.linkedin.com/posts/pdewit83_azure-powershell-semver-share-7458263169749303296-xT7e/?utm_source=social_share_send&utm_medium=ios_app&rcm=ACoAAAFfvOEBEIh09mNz8UmCcWHASNGTPiazL_I&utm_campaign=copy_link

Today my pipeline broke on this:

[Az.Storage](http://az.storage/) 𝟵.𝟲.𝟬
→ requires Az.Accounts >= 𝟱.𝟯.𝟮

[Az.Storage](http://az.storage/) 𝟵.𝟲.𝟭 (PATCH release)
→ suddenly requires Az.Accounts >= 𝟱.𝟰.𝟬 (which is a minor release)

And that dependency change was not even mentioned in the release notes.

My pipeline blocked it immediately, as it should.
I pin exact module versions and only allow automatic patch updates.
Minor versions go through validation first.

That is standard enterprise CI/CD practice. This is why semantic versioning matters.

Without strict dependency discipline, semantic versioning becomes meaningless.

[Microsoft](https://www.linkedin.com/company/microsoft/):
A patch release should not introduce new minor-version dependency requirements. Especially not without explicitly documenting it in the release notes.

How are others handling Az module updates?

Strict version pinning?
Automatic minor updates?
Or full isolation/containerization?

### Issue script & Debug output

```PowerShell
dependency no doc
```

### Environment data

```PowerShell
PS 7
```

### Module versions

```PowerShell
Az.storage
```

### Error output

```PowerShell

```