Juju cannot add machines from 'daily' image stream on Azure

[Jack Shaw]

Replicated on juju 3.4, but likely a wider issues

NOTE: This only applies to bases prior to Noble

```
$ juju bootstrap azure
$ juju add-model m
$ juju model-config image-stream=daily
$ juju add-machine --base ubuntu@22.04
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
m azure-centralus azure/centralus 3.4.3.1 unsupported 11:45:37+01:00

Machine State Address Inst id Base AZ Message
0 down pending ubuntu@22.04 Ubuntu SKUs for daily stream not found
```

I believe this is because of changes to how Canonical publishes images to azure

This is the problem area:
https://github.com/juju/juju/blob/4d6ece0f954a9071a567a7c828e3bb70e3228a94/provider/azure/internal/imageutils/images.go#L117-L118

From these lines of code we can see that Juju assumes that, say, jammy, daily images are published to the same offer `001-com-ubuntu-server-jammy` offer, with an sku ending `daily` or `daily-lts`

However, from running `az vm image list --publisher Canonical --output table --all` (note: this command takes a long time) we can see this is not true.

Daily jammy images are instead published to a different offer, with id `0001-com-ubuntu-server-jammy-daily`

[Jack Shaw (jack-shaw)]

https://github.com/juju/juju/pull/17465