Support for taking ownership of resources managed by k0s

[iawia002]

Description

Especially for the CoreDNS config, there'd be another option that bypasses the k0s config: We could offer a way for users to just take ownership of the ConfigMap, for example. Say adding a label or annotation to it that tells k0s to not overwrite it.

Part of #5800 (comment)

ref #4021

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

[github-actions]

This pull request has merge conflicts that need to be resolved.