Track upstream issue about flatcar ignition current issues

[primeroz]

Motivation

Follow up to #1659

There is an issue currently with Ignition configuration for flatcar in CAPI kubernetes-sigs/cluster-api#7679 forcing us to create a suboptimal configuration

• FileSystem and mounts definition must be specified in the KubeadmConfigspec https://github.com/giantswarm/cluster-azure/pull/81/files#diff-89953cc6f68ecb2458c26ea9af45c03b11f68f3424c8379fff1d340dff126ccfR44
• Paritioning of disks must be specified as an ignition additional config https://github.com/giantswarm/cluster-azure/pull/81/files#diff-89953cc6f68ecb2458c26ea9af45c03b11f68f3424c8379fff1d340dff126ccfR75

This is suboptimal and confusing, we should track the fix upstream and change to a consistent configuration when fix is available

TODO

• Track upstream fix ( Possibly push a fix for it )
• Convert our configuration to a consistent one

Outcome

For Clippy

• we have a less confusing configuration in cluster-azure for storage management