Use KRM based k8s applier

[raliev12]

Problem description (if applicable)
Currently, k8s applier code is a part of airshipctl core functionality. However, this implementation is bulky, contains a lot of useless abstractions and imposes on us many restrictions and inconveniences. Among them:

1. dependencies in airshipctl core functionality
2. impossible to use or choose different backends for apply
3. no appropriate log integration with k8s libs (lack of debug information of apply process)
4. no possibility of granulated upgrade of cli utils dependencies

Proposed change
Use KRM function for apply process. Proposed change - https://review.opendev.org/c/airship/airshipctl/+/809291

Potential impacts
None.

[raliev12]

This one can be assigned to me.