bring back support for container registry secrets from v1
V1 supported generating a dockerconfigjson secret automatically from parameters passed to the action (container-registry-url,container-registry-username etc.), and in v2 that was changed to requiring users to add their own secret data manually. This made our most common use pattern, container registry secret creation, significantly more complex as the user has to go run kubectl outside the action to generate a secret every time.
-Refactor to use kubernetes-client/javascript to remove kubectl dependency management
-Remove dependency on L2 integration tests
-Create minikube integration testing in github actions to remove L2 secrets requirements
Brandon Foley
Vidya Reddy
David Gamero