feat: display invalid config on a new node at boot end

[mauromorales]

When bootstrapping a node, if there's an error it can be hidden by the qr code at the end of the booting. Instead it would be better if the issues show after the qr code.

[jimmykarily]

Can we put some reproducing steps here?

[mauromorales]

@jimmykarily as far as I understand, the steps are:

• Generate a broken cloud config
• Build a standard image with the cloud config
• Boot

You'd expect the node to configure itself with the given cloud config, instead it shows the QR code as if you'd want to configure it at this point. Apparently there's a message with the error, but it gets hidden by the QR code making it seem like there was no error at all

[mauromorales]

@wrkode let me know if I describe the situation correctly ^^

[wrkode]

Absolutely, In practice, the issue is that there's no clear way (at boot time) to see that the config file syntax or typos are causing an error. Ideally the final state/error should be shown under the QR Code.