Port module refactoring + new template to project

[nmiodice]

Description

As a consumer of Cobalt, I'd like to leverage the latest learnings from projects that have used Cobalt for real deployments in order to incorporate learnings into my IAC projects.

Acceptance Criteria

Reference: [Done-Done Checklist] (https://github.com/Microsoft/code-with-engineering-playbook/blob/master/Engineering/BestPractices/DoneDone.md)

• [x] pre-jan commit (we need to identify which one) should be tagged at 1.0.0
• [ ] If breaking changes are made, we should tag at 2.0.0
• [x] ~If breaking changes are not made, we should tag at 1.1.0~
• [x] All existing modules are pulled into the OSS repo
• [x] All tests should continue to pass
• [x] All apache license headers are removed

Resources

• semver

Notes

• The proposed change will result in pulling in new modules that are not shown by example through a template. Follow up stories to implement a template that uses these new modules can be and should be added to the backlog.

[nmiodice]

@ThePhen @TechnicallyWilliams @AdanOrtiz does this commit seem OK for the 1.0.0 tag? https://github.com/microsoft/cobalt/commit/05458852635a59494ca90e309b6e2d82d64883fb

[nmiodice]

We will use this commit ^^

[nmiodice]

v1.0.0 tag: https://github.com/microsoft/cobalt/tree/v1.0.0

[nmiodice]

We will wait to tag with v2.0.0 until https://github.com/microsoft/cobalt/issues/373 and the PR teardown is re-enabled