Resolve issue with api-keys and logger

[jayjaybunce]

🗣 Description

• Reworked a logger to allow api-keys in requests and only instantiate on requests we setup to log

💭 Motivation and context

• Resolves issue with the backend tests failing and was failing to deploy to staging, initial PR was merged and issue found when testing in staging
• https://maestro.dhs.gov/jira/browse/CRASM-569

🧪 Testing

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All future TODOs are captured in issues, which are referenced
  in code comments.
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING 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

• Revert dependencies to default branches.
• Finalize version.

✅ Post-merge checklist

• Create a release.

[aloftus23]

looks good

[ameliav]

Worked for me after walking through the updates with Janson.
It resulted in logs that could be filtered to show the payload with who was invited and by whom.