Workloads Map Expansion

[jmarhee]

I'd like to change this current implementation to do:

• A nested block of "required" workloads (cni, storage, lb, ingress) if selected, and additional (things the user would define to add on, service meshes, etc.) rather than locking the customizability into just those options with only the release URL changing.

[jmarhee]

#87 Addresses cni and additional and ingress.

[displague]

We're going to revisit this idea by combining learning from https://github.com/equinix/terraform-metal-anthos-on-baremetal#storage-providers and https://github.com/aws-ia/terraform-aws-eks-blueprints#amazon-eks-blueprints-for-terraform.

Effectively, we would like to create a module of curated and opinionated reusable Equinix Metal Kubernetes addon modules.

This will include, for example, Cloud Provider Equinix Metal, the Cluster API provider, KubeVIP, and MetalLB.
Storage providers would also be provided.

These modules would be housed in a new project and would be consumed by projects like our K8s, K3s, Anthos, EKS, and other Kubernetes integrations.

I'm going to leave this issue open until we have a dedicated home for these modules.