Local registry

[lizardruss]

What issue type does this pull request address? (keep at least one, remove the others)
/kind feature

What does this pull request do? Which issues does it resolve? (use resolves #<issue_number> if possible)
Adds a local image registry when user lacks push permissions to the remote registry.

Please provide a short message that should be published in the DevSpace release notes
Fixed an issue where DevSpace ...

What else do we need to know?

TODO

• Detect push permissions
• Deploy registry
• Wait for Registry to be ready
• Start port forwarding
• Rewrite image tag for deployed registry
• Build / Push image
• Update runtime variables
• Update config substitution
• Update ShouldRebuild() to account for local registry usage
• Acceptance Tests:
  • get_image output
  • ${runtime.images.my-image.image} && ${runtime.images.my-image}
  • image(name)
  • kubectl deployment rewritten
  • helm deployment rewritten
  • dev.*.imageSelector (and all the other different runtime rewritten config sections)
  • dev.*.devImage
• Move local registry configuration to top level (avoid duplicating for multiple images)
• Add progress indicator when transferring images
• devspace init doesn't produce config for local-registry (even in comments).
• devspace build on minikube with default config(no config for local-registry) spins the registry pod doesn't push the image to it and devspace build command errors out. (Note: updated to skip push for devspace build and minikube, as well as skip local registry for minikube)
• devspace cleanup local-registry command asks question (sure to cleanup) even when there is no registry pod running.
• logs need formatting