Removed imagePullPolicy and added namespace to local config

[ehearneRedHat]

Problem:

• The imagePullPolicy was preventing the pods from pulling the image from the user's specified repository, causing a ImageNeverPull error.
• The generated secret from aws-credentials.env was not able to be accessed by pods in the kuadra-system namespace as the secret was generated in the default namespace, causing a CreateContainerConfig error.

Solution:

• Removing imagePullPolicy from config/local/manager_config_patch.yaml , allowing the pods to pull the image from the user's specified repository.
• Adding the kuadra-system namespace to config/local/kustomisation.yaml , ensuring the secret is accessible within the kuadra-system namespace for pods which allows the pods to run.

How to reproduce the error (main branch):

# Set up and run the cluster
kind create cluster
make install
IMG=quay.io/<namespace>/kuadra:v1 make docker-build docker-push deploy-local
# Check for imagePullPolicy error
kubectl -n kuadra-system get pods
# Remove imageNeverPull from deployment config
kubectl -n kuadra-system edit deploy kuadra-controller-manager
# Once removed, check for CreateContainerConfig error
kubectl -n kuadra-system get pods
kind delete cluster

How to confirm error is resolved (on deploy-local branch):

# Set up and run the cluster
kind create cluster
make install
IMG=quay.io/<namespace>/kuadra:v1 make docker-build docker-push deploy-local
# Check for imagePullPolicy error
kubectl -n kuadra-system get pods

[R-Lawton]

@dlaw4608 When you get a chance do you want to review this to?

[dlaw4608]

@ehearneRedHat just approved the changes there