Set Rails logging context independent of Sentry

[kayline]

Summary

• This work is behind a feature toggle (flipper): NO
• (Summarize the changes that have been made to the platform)
• Separate controller concerns for configuring Rails logging context and Sentry logging context. Allow teams not using Sentry to only pull in the Rails logging code.
• (Which team do you work for, does your team own the maintenance of this component?)
• Decision Reviews, No. This is shared platform code, but we use it in our module.

Related issue(s)

• Disambiguate Sentry and Rails logging context in main ApplicationController va.gov-team#102065

Testing done

• New code is covered by unit tests
• Describe what the old behavior was prior to the change
• A single method in the SentryControllerLogging concern set both Sentry context and Rails logging context, triggered by a :before filter. Now there are two concerns and two methods, clearly named, and every place that was calling the old one is now calling both. Code that was overriding the old method is now overriding the new name for that method.
• Describe the steps required to verify your changes are working as expected. Exclusively stating 'Specs run' is NOT acceptable as appropriate testing
• Ensure logs in datadog retain all their context

What areas of the site does it impact?

(Describe what parts of the site are impacted andifcode touched other areas)
Additional context included in controller logs

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

[github-actions]

Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: app/controllers/concerns/controller_logging_context.rb

[github-actions]

Error: A file (or its parent directories) does not have a CODEOWNERS entry. Please update the .github/CODEOWNERS file and add the entry for the Offending file: app/controllers/concerns/controller_logging_context.rb

[rmtolmach]

I'm on an alphabetization kick recently... would you mind moving this up above line 34 so it's perfectly alphabetized?

The assignment/owner looks right 👍

[kayline]

Fixed!

[ATeal]

LGTM 👍

[rmtolmach]

The final file that needs a review is modules/apps_api/app/controllers/apps_api/application_controller.rb, but that module seems orphaned. So I'll override the need for that review and merge this PR.