Fargate service hostname routing & updates

[rnzsgh]

This PR adds the following enhancements:

• Run CodeBuild stage in private subnet in VPC with app security group so that DB access is possible for testing or schema migrations

• When adding additional Fargate services to a cluster create a new ECR repository for each service

• New Fargate services can route by hostname or path in ALB

• For additional Fargate services, if hostname and zone are specified a new record is created in Route 53

• New Fargate regions for one-click deployments

• Update the bastion host AMIs

• Update the Elastic Beanstalk stacks

• Update the wrapper template default bucket version

[rnzsgh]

I agree that the network stack name parameter is not great. I used the same parameter name that was in the EB CFN template. We should consider renaming those. They will break backwards compatibility, but I don't see an issue.

[rnzsgh]

Actually, I added the regexs to a ticket and will deal with in the current sprint.