Create the autopilot client before applying the plan

[twz123]

Description

If it's done the other way round, it might happen that the k0s binary is being replaced by the autopilot update process, and cannot be executed.

This prevents errors like this:

Process exited with status 126: "sh: /usr/local/bin/k0s: Permission denied"

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[jnummelin]

OMG, I've been banging my head with this same thing on my grab backport fix attempts