Drop k0sctl integration test

[twz123]

Description

The k0s CI uses k0sctl in several places these days: The nightly check-network workflow, the OS testing matrix, and most importantly, the release pipeline. The individual k0sctl integration test is no longer needed.

@k0sproject/k0s-maintainers feel free to close the PR if you'd prefer to keep the test.

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