Draft: Skip failed job about merge_requests_helper_spec

What does this MR do and why?

Skip failed job: https://jihulab.com/gitlab-cn/gitlab/-/jobs/7404150

The bug is from Upstream, waiting for their fix: https://gitlab.com/gitlab-org/gitlab/-/jobs/4162534333

Failures:
  1) MergeRequestsHelper#diffs_tab_pane_data for endpoint_diff_for_path when default project namespace returns expected values
     Failure/Error:
       expect(
         subject[:endpoint_diff_for_path]
       ).to include("/#{namespace}/-/merge_requests/#{merge_request.iid}/diff_for_path.json")
       expected "/namespace5/project1/-/merge_requests/1/diff_for_path.json" to include "/namespace1/project1/-/merge_requests/1/diff_for_path.json"
     # ./spec/helpers/merge_requests_helper_spec.rb:47:in `block (5 levels) in <main>'
     # ./spec/spec_helper.rb:427:in `block (3 levels) in <top (required)>'
     # ./spec/support/sidekiq_middleware.rb:18:in `with_sidekiq_server_middleware'
     # ./spec/spec_helper.rb:419:in `block (2 levels) in <top (required)>'
     # ./spec/spec_helper.rb:415:in `block (3 levels) in <top (required)>'
     # ./lib/gitlab/application_context.rb:61:in `with_raw_context'
     # ./spec/spec_helper.rb:415:in `block (2 levels) in <top (required)>'
     # ./spec/spec_helper.rb:242:in `block (2 levels) in <top (required)>'
     # ./spec/support/system_exit_detected.rb:7:in `block (2 levels) in <main>'
     # ./spec/support/database/prevent_cross_joins.rb:108:in `block (3 levels) in <main>'
     # ./spec/support/database/prevent_cross_joins.rb:62:in `with_cross_joins_prevented'
     # ./spec/support/database/prevent_cross_joins.rb:108:in `block (2 levels) in <main>'
     # ./jh/spec/spec_helper.rb:30:in `block (3 levels) in <main>'
     # ./jh/spec/spec_helper.rb:30:in `block (2 levels) in <main>'
Finished in 8.9 seconds (files took 48.92 seconds to load)
3 examples, 1 failure
Failed examples:
rspec ./spec/helpers/merge_requests_helper_spec.rb:45 # MergeRequestsHelper#diffs_tab_pane_data for endpoint_diff_for_path when default project namespace returns expected values

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.