Should we create new repositories in the gomods organization for deployment artifacts?

**Is your feature request related to a problem? Please describe.**

We discussed in the [September 27, 2018 dev meeting](https://docs.google.com/document/d/1xpvgmR1Fq4iy1j975Tb4H_XjeXUQUOAvn0FximUzvIk/edit#heading=h.f24qbjkyfv6v) that folks are starting to work on Terraform configuration to deploy Athens. When this is done, the `gomods/athens` repository will have helm charts and terraform configuration.

**Describe the solution you'd like**

I wonder if we should create separate repositories inside the `gomods` GitHub organization to house artifacts for each different deployment/configuration system?

**Describe alternatives you've considered**

We could put all the deployment artifacts into the `gomods/athens` repository?

**Additional context**

We discussed this in the September 27, 2018 Athens dev meeting, and I think @timraymond mentioned the terraform configs.

Review the September 27, 2018 dev meeting discussion and the issue's alternatives. Compare separate gomods repositories for Helm and Terraform artifacts with keeping deployment artifacts in gomods/athens; done means the repository organization decision is documented and agreed.

Written by the indexing model from the issue text.