Unable to see provisioning errors on RKE2 clusters

[gaktive]

Internal reference: SURE-5141 though it's purely internal Reported in 2.6.7 from @bashofmann

Issue description: If you make a configuration error in the machine pool config which makes the VM creation fail, it’s very hard to see the error message from the provider. The error message maybe pops up for a split second and then Rancher directly deletes the machine and retries the creation, which then fails again. The user could not find any other place where the error messages are logged more permanently. Ticket with video to show the behaviour: https://github.com/rancher/rancher/issues/38159

Repro steps:

• Create a RKE2 cluster on an infrastructure provider, such as Azure
• Provide an invalid configuration for the machine pool, for example by providing an invalid image like "canonical:UbuntuServer:1.04-LTS:latest"
• The cluster is created and a machine is created and then directly deleted again and recreated
• The error message from Azure only is visible for a split second
• There is no permanent and easy way to actually see and read the error message

Workaround: none

Actual behavior: Error messages are only shown for a split second.

Expected behavior: Error messages are shown permanently until they are fixed.

[gaktive]

This will require backend first before the UI can do anything.

[gaktive]

Backend not targeted until 2024 Q1 potentially. Pushing to 2.7.x as a generic placeholder.