Broken master: ./spec/features/merge_request/user_sees_pipelines_spec.rb

From https://gitlab.com/gitlab-org/security/gitlab/-/jobs/930345063:

  1) Merge request > User sees pipelines race condition when pipeline and merge request were created simultaneously user sees pipeline in merge request widget
     Failure/Error: Experiments::RecordConversionEventWorker.perform_async(:ci_syntax_templates, current_user.id)
     Sidekiq::Worker::EnqueueFromTransactionError:
       `Experiments::RecordConversionEventWorker.perform_async` cannot be called inside a transaction as this can lead to
       race conditions when the worker runs before the transaction is committed and
       tries to access a model that has not been saved yet.
       Use an `after_commit` hook, or include `AfterCommitQueue` and use a `run_after_commit` block instead.
     # ./config/initializers/forbid_sidekiq_in_transactions.rb:23:in `block (2 levels) in <module:NoEnqueueingFromTransactions>'
     # ./app/services/ci/create_pipeline_service.rb:124:in `record_conversion_event'
     # ./app/services/ci/create_pipeline_service.rb:86:in `execute'
     # ./spec/features/merge_request/user_sees_pipelines_spec.rb:245:in `block (5 levels) in <top (required)>'
Finished in 10 minutes 47 seconds (files took 42.52 seconds to load)
599 examples, 1 failure
Failed examples:
rspec ./spec/features/merge_request/user_sees_pipelines_spec.rb:251 # Merge request > User sees pipelines race condition when pipeline and merge request were created simultaneously user sees pipeline in merge request widget

This change came in !48141 (merged). How is this not breaking in production?

Edited by Stan Hu