Reporter: convert to class implementation (issue 166)

[rlxdev]

🗣 Description

I converted the reporter module to a class. It’s instantiated by the Orchestrator class in the run_reporter() method. There are a few methods in the reporter that format HTML independent of the instance, so these are implemented as static methods.

If you’re reviewing the changes, it’ll be easier to compare this class implementation with the non-class module while ignoring whitespace and empty lines.

💭 Motivation and context

closes #166

🧪 Testing

I've tested these changes by running several different variations of ScubaGoggles runs. All runs I've done were successful. Nearly all changes were associated with converting the reporter functions to class methods, so there weren't any functional changes to the code that would cause any problems.

✅ Pre-approval checklist

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

✅ Pre-merge Checklist

• This PR has been smoke tested to ensure main is in a functional state when this PR is merged.
• Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge Checklist

• Delete the branch to clean up.
• Close issues resolved by this PR if the closing keywords did not activate.

[mitchelbaker-cisa]

Looks good Roy. Generated a few scubagoggles reports via service account with no issue.