Automatically redact logs when GitLab instance is in FIPS mode
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal GitLab should redact logs automatically when an instance is in FIPS mode in order to keep sensitive data such as usernames, email addresses, IP addresses, and domain names from being logged. Ideally this could be configured with some granularity in a future iteration so customers can choose what to include and exclude in logs. Many customers, namely US government customers, have data secrecy requirements that prohibit them from sharing logs with this information. Due to these restrictions, these customers are either not permitted to share logs with Support, or the admin must redact logs themselves before sharing with us. Manual redaction is often incomplete/imperfect so protected information can still leak, leading Support to have to redact tickets and leaving GitLab admins to follow their internal data leakage procedures. If possible, this should be avoided. Additionally, this feature may permit more organizations to be able to share logs with Support, improving customer experience, Support experience, and lowering time to resolution. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->
issue