[CA lifecycle] Allow caCert override on MachineRegistration #859
Description
Currently the elemental-operator always reads the cacerts Rancher settings value when populating the MachineRegistration's caCert and then when creating the elemental-system-agent connection file.
It should be possible for users to create (and edit) MachineRegistrations with this value pre-filled.
The elemental-operator should then use it when configuring all agents (elemental-register, elemental-system-agent, rancher-system-agent).
In this way, the user no longer needs to inject a private CA cert into the system image, and will allow users to still enforce strict validation, while having a very convenient way of propagating their desired certificate to machines.