Merge pull request juju#16135 from hpidcock/fullstatus-with-storage

juju#16135

Instead of `juju status --storage` making 3 seperate facade calls in addition to the FullStatus call, instead return the information in the FullStatus facade call.

This also implements server side filtering on unit/application for storage entities.

## QA steps

- Deploy multiple apps with storage.
- Check `juju status` without storage
- Check `juju status --storage`
- Check `juju status --storage` works against old controller (Client facade <= 6)
- Check `juju status --format yaml` (should have implicit --storage)
- Check `juju status --storage <filter>`

Example no filter:
```
juju status --storage
Model Controller Cloud/Region Version SLA Timestamp
a minikube minikube 3.2.3 unsupported 16:13:46+10:00

App Version Status Scale Charm Channel Rev Address Exposed Message
b waiting 1 postgresql-k8s 14/stable 73 10.110.113.233 no installing agent
postgresql-k8s waiting 1 postgresql-k8s 14/stable 73 10.104.229.135 no installing agent

Unit Workload Agent Address Ports Message
b/0* blocked idle 10.244.0.6 failed to create k8s resources
postgresql-k8s/0* blocked idle 10.244.0.7 failed to create k8s resources

Storage Unit Storage ID Type Pool Mountpoint Size Status Message
b/0 pgdata/1 filesystem kubernetes /var/lib/postgresql/data 1.0 GiB attached Successfully provisioned volume pvc-f08518a7-20be-4184-bc50-e668baa7fa37
postgresql-k8s/0 pgdata/0 filesystem kubernetes /var/lib/postgresql/data 1.0 GiB attached Successfully provisioned volume pvc-48b7f0ea-b103-4d66-b21e-b69d107a072d
```

Example with filter:
```
juju status --storage b
Model Controller Cloud/Region Version SLA Timestamp
a minikube minikube 3.2.3 unsupported 16:16:27+10:00

App Version Status Scale Charm Channel Rev Address Exposed Message
b 14.7 waiting 1 postgresql-k8s 14/stable 73 10.110.113.233 no installing agent

Unit Workload Agent Address Ports Message
b/0* blocked idle 10.244.0.6 failed to create k8s resources

Storage Unit Storage ID Type Pool Mountpoint Size Status Message
b/0 pgdata/1 filesystem kubernetes /var/lib/postgresql/data 1.0 GiB attached Successfully provisioned volume pvc-f08518a7-20be-4184-bc50-e668baa7fa37
```

## Documentation changes

N/A

## Bug reference

Partially mitigates https://bugs.launchpad.net/juju/+bug/2015371

JUJU-4538

Merge pull request juju#16307 from juju/dependabot/pip/acceptancetest…

…s/cryptography-41.0.4

juju#16307

Bumps [cryptography](https://github.com/pyca/cryptography) from 41.0.3 to 41.0.4.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst">cryptography's changelog</a>.</em></p>
<blockquote>
<p>41.0.4 - 2023-09-19</p>
<pre><code>
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL 3.1.3.
<p>.. _v41-0-3:
</code></pre></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/pyca/cryptography/commit/fc11bce6930e591ce26a2317b31b9ce2b3e25512"><code>fc11bce</code></a> bump for 41.0.4 (<a href="https://redirect.github.com/pyca/cryptography/issues/9629">#9629</a>)</li>
<li>See full diff in <a href="https://github.com/pyca/cryptography/compare/41.0.3...41.0.4">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=cryptography&package-manager=pip&previous-version=41.0.3&new-version=41.0.4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/juju/juju/network/alerts).

</details>

Merge pull request juju#16234 from juju/dependabot/github_actions/bal…

…chua/microk8s-actions-0.4.1

Bump balchua/microk8s-actions from 0.4.0 to 0.4.1