Templatize via Cookiecutter for enhanced audience utility

[d33bs]

This PR addresses #4 by moving to a Cookiecutter implementation for this repository. The benefit of this change entails making this template more accessible through Cookiecutter commands and more efficient through common text replacements which would otherwise need to be performed manually.

Note: After this is merged I plan to remove the Github template status (which will no longer be as helpful or accurate to the intent).

A demonstration of the audience experience after a merge can be found from the following command:

python -m cookiecutter https://github.com/d33bs/gc-cloud-storage-bucket.git --checkout templatize-via-cookiecutter

Thanks in advance for any thoughts and comments you may have!

Closes #4

[falquaddoomi]

I can see the value in using cookiecutter to customize the names of files and strings in documentation. In the case of Terraform config, I'd personally opt for one of Terraform's existing methods for setting input variables (https://developer.hashicorp.com/terraform/language/values/variables#assigning-values-to-root-module-variables) rather than writing them into the default value fields within your modules. Typically, you'd create a terraform.tfvars file in the folder where you expect your users to invoke Terraform and instruct them to modify it; you could also populate it with cookiecutter.

[d33bs]

Thank you @falquaddoomi ! I've added a terraform.tfvars file as you suggested and along with other updates.

[vincerubinetti]

Reviewed writing, LGTM

[falquaddoomi]

Oof, sorry, forgot to submit this review. There's just the one thing about the .tfvars file needing to be renamed to something TF will automatically use, but otherwise this all looks great!

[falquaddoomi]

Looks good! Thanks for taking my previous suggestions into consideration.

[d33bs]

Thank you @falquaddoomi and @vincerubinetti for your reviews! Merging this in now.