Incorporate Reference Modules into MC

[jl-0]

Would like to add a new feature to include reference deployment modules in the MC to simplify the process of creating marketplace ready apps for simple deployments.

To begin it seems like a "ECS Service" deployment would be fairly straightforward. I'd like to pattern off the current Portal terraform (https://github.com/unity-sds/unity-uiux-infra/blob/main/terraform-unity-portal).

I'd like the software package to only need to specify the particulars of their software, nothing specific to the deployment environment. For the portal it might look something like the following:

module "mdps_ecs_service_pattern" "portal" {
  url_path = ['portal']
  port_num = [8080]
  container_definitions = templatefile("${path.module}/task.definition.json", local.task_def_vars)
  cpu = 256
  memory = 512
}

The rest of the details are handed by the design pattern. I'd also like it if there is a venue level ECS that these services are run from (perhaps it's own market place item that is installed with bootstrap).

Since we already have the venu-level proxy I'm thinking each service gets its own ALB, TG, etc. so that there are no port conflicts and we update the httpd configs just like we do today. We could also have a single ALB and use path based mapping, but I think that forces us to have another item in the path, e.g. "/unity/dev/services/{service name}". Maybe review that as well because it would save costs and I don't think we'll be close to reaching the limit of target groups and listeners.

[jl-0]

@hargitayjpl @jdrodjpl I assigned both of you because I think you might want to discuss first then divide up the work. Perhaps once there is a top-level architecture Josh could make the MC updates and Brandon work on developing the common marketplace items (like venue ECS, EKS, etc.)