Update gitlab-labkit to v0.30.1
What does this MR do and why?
See https://gitlab.com/gitlab-org/ruby/gems/labkit-ruby/-/releases/v0.30.0
The only relevant change for gitlab-rails is this issue: gitlab-org/ruby/gems/labkit-ruby#34 (closed)
We now fail fast in dev and tests if an event is logged using a log key that we know would be overwritten once the event leaves the rails app, because we have other systems enrich these events as they propagate through the log stack. This was originally found in !111285 (merged).
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.