Comment 9 for bug 1961620

I chatted with subiquity folks today. If subiquity is passing cloud-config user-data straight into cloud-init in all cases for the next boot, there could be problems with custom bootcmd, runcmd and or snap configuration issues that may not like working in chroots. Performing all cloud-init initialization during ephemeral boot and a pivot may not make sense for all cases, but it minimally makes sense for cloud-init to break if it has awareness of a significant mount that is missing.