Precursor to initial functionality

[nickviola]

🗣 Description

First commits PR prepping the repository.

💭 Motivation and context

Beginning of the tpt-report repo codebase.

🧪 Testing

Baseline skeleton testing. More code to come.

✅ Pre-approval checklist

• [x] This PR has an informative and human-readable title.
• [x] Changes are limited to a single goal - eschew scope creep!
• [x] All future TODOs are captured in issues, which are referenced in code comments.
• [x] All relevant type-of-change labels have been added.
• [x] I have read the CONTRIBUTING document.
• [x] These code changes follow cisagov code standards.
• [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• [x] Tests have been added and/or modified to cover the changes in this PR.
• [x] All new and existing tests pass.

✅ Pre-merge checklist

• [ ] Revert dependencies to default branches.
• [ ] Finalize version.

✅ Post-merge checklist

• [ ] Create a release.

[coveralls]

Pull Request Test Coverage Report for Build 5811026629

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-100.0%) to 0.0%

---

Totals
Change from base Build 5535664291:	-100.0%
Covered Lines:	0
Relevant Lines:	0

---

💛 - Coveralls

[schmelz21]

Generally, we expect the first PR to get the repo to some functional state; more than just renaming files from the skeleton. It should do something useful, even if it's a super bare-bones version of what the repo will eventually become.

@nickviola , @JCantu248 , @ameliav - For the sake of bare-bone functionality, can we add in the functions from staging get_json_file, parse_json and update Usage. Correct me if I am wrong, but this will take in the report data and have it ready for the report generation which can be in a follow-up PR.

[JCantu248]

Unit test cases will be implemented with the upcoming PR for Issue: https://github.com/cisagov/tpt-reports/issues/6