Build/test with docker images

[yzhang-23]

We are planning to build/test all repos with docker images using GitHub actions. Before we deploy these actions, we must make the following points clear:

1. Should we build a big image which can be used to build all repos, or we build individual small images for every repo.
2. Which registry should we keep these images, a private registry owned by some developer, or a common registry easily accessed by all?
3. Which type of TOKENs should we used to push/pull these images?

[ryanmrichard]

1. I think the question should be whether we want one giant base image (which has all possible base configurations) or if we want one base image per configuration. I'm inclined to lean towards the latter unless anyone has a reason why we should prefer the former. Downstream we will be having images per repo, if for no other reason besides each downstream repo is an independent product.

2. They should not be stored in private registries owned by a developer. They should be associated with the NWChemEx-Project, if they're on GitHub. If they're going to live off GitHub we want to make an NWChemEx-Project account on the other website (which should probably be done by @twindus when we're ready to do so).

3. What are the choices? If we can get by with the tokens generated automatically by GitHub actions go with those.