Refactor All Rego

[adhilto]

🗣 Description

• Move all shared rules/functions to the Utils.rego file
• Make all Rego code v1 compliant
• Make all Rego code conform to our Regal style checks

💭 Motivation and context

Closes #117.
Closes #69.

🧪 Testing

Tests I performed:

• .\regal.exe lint --format github rego Testing passes (using the config file in the .regal folder)
• .\opa_windows_amd64.exe check --rego-v1 rego Testing passes
• Rego unit tests all pass
• Ran ScubaGoggles for all products on both main and this branch, no diff observed

✅ 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.

[LaurenBassett]

Is this for all or just calendar?

[adhilto]

Is this for all or just calendar?

Sorry I should have made a note about that. It's for all. It started out as just calendar (hence the branch name) but I ended up doing it all.