cloud-init resize fails due to unexpected output format changes in btrfs
--version output since 6.10.

This causes cloud-init to fail to parse the version, throwing an error, and
skipping resizefs execution.

This is an upstream bug which have already been fixed by upstream, and the
latest cloud-init release should have included the fix.

https://github.com/canonical/cloud-init/issues/5614

This is not actually a big issue when using microos based image in a cloud vm
scenario, due to systemd-growfs being setup in the image dracut.conf.d.
but it's an annoyance, because the systemd service status is degraded for
cloud-init due to this.