Refactor Gmail Rego

[adhilto]

🗣 Description

Refactor Gmail Rego to comply with current style best-practices.

💭 Motivation and context

Closes #116.

🧪 Testing

• Rego unit tests pass
• Compared refactored results with results from main -- no difference.

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

[buidav]

Ran .\opa_windows_amd64.exe check --rego-v1 to check for OPA v1 compatibility. The flag is only available for OPA executables greater than 0.59. It came back with only one thing :). Fix before merging. Everything else runs perfectly.

[snarve]

Looks good!