feat: Converge kubeconfig / aws code in infrastructure

[qdzlug]

Is your feature request related to a problem? Please describe. The reorganization process split several pieces of logic into two main paths:

1. Logic for working with an AWS managed infrastructure stood up via this process.
2. Logic for working with a kubeconfig file (for any other k8 cluster).

Additionally, there are two separate ingress controller deployments:

1. An AWS based deployment that uses ECR and allows building a custom controller or pulling from the NGINX registry.
2. A JWT only process that is only used with kubeconfig and can only pull the NGINC Plus IC currently.

Describe the solution you'd like Code for both of these paths to be converged into one set of scripts / stacks.

Describe alternatives you've considered None.

Additional context Part of this process requires the refactoring of the IC build / pull process to use registries other than ECR.

[qdzlug]

#167 has addressed this issue for AWS, DO, and Linode.

Other support still in progress.