Move localkube controller to localkube repo

[ethernetdan]

Currently the code which manages localkube lives in the spread repository. Problems around which repo to create an issue arise from having localkube functionality across multiple repos.

Requirements:

• We should move all functionality to the localkube repository and export a *cli.Command which can be included in spread. It should allow for all current functionality.
• The functionality should be in it's own new package to minimize the required dependency.

[ethernetdan]

Completed rewriting the localkube launcher within my localkube fork. I ran into an issue trying to compile spread with the controller where duplicate vendored dependencies were included from the /vendor folder of the localkube repo.

Potential solution I've thought of:

• maintaining a branch with the vendor directory removed
• vendoring localkube in spread such that the localkube /vendor path is not used