Comment 2 for bug 1838032

We just had some internal conversation about this, which I will do my best to summarise here.

Ryan agreed that this would make debugging easier, but worried about removing cloud-init.log as it's a well established path that people rely on. He identified that `cloud-init analyze` was one example of something that would need to be modified to not rely on cloud-init.log.

I noted that I wasn't intending this as a proposal to drop cloud-init.log. I noted that we're going to need to support non-systemd instances using cloud-init.log anyway, so we won't be able to drop those code paths regardless. I noted that `cloud-init collect-logs` may need updating.

I proposed the following plan for Ubuntu: emit to both cloud-init.log and the journal in 20.04 LTS, and discuss dropping cloud-init.log for 22.04 LTS.