Remove `multiple_http_integrations_custom_mapping` feature flag [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!56021

Remove `multiple_http_integrations_custom_mapping` feature flag

Show branch info in DAST profiles library

See merge request gitlab-org/gitlab!56019

Add branch information to the DAST profiles library.

Remove incorrectly added optional params from Project update params [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!56180

Remove incorrectly added optional params from Project update params [RUN ALL RSPEC] [RUN AS-IF-FOSS]

Change members to billable members in frontend

See merge request gitlab-org/gitlab!55824

Reapply !53803 Allow saving repository weights after a storage has been removed - [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!55689

Add Postman API specification mode to API fuzzing CI configuration page

See merge request gitlab-org/gitlab!55601

Now that the Secure stage namespace documentation has been merged we
should be making use of it.

Introduce MarkerRange class [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!55669

Create dast_failed_site_validations feature flag [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!56146

Info about the gitlab.com KAS instance

See merge request gitlab-org/gitlab!55593

Boards new list for Assignee

See merge request gitlab-org/gitlab!56151

Fix file locking e2e tests

See merge request gitlab-org/gitlab!56307

Revise bad warning message: remove comma splice

See merge request gitlab-org/gitlab!56115

Fix malformed sentence in the warning shown when a user tries to
edit a comment that has changed.

Fix typo in wiki.rb

See merge request gitlab-org/gitlab!56285

In this commit we fix a typo (`reponse` vs. `response`) and
also the method call `response_api_error!` that was lacking
one argument.

Improve MR Retarget Chain to prefer usage of `MR::DeleteSourceBranchWorker`

See merge request gitlab-org/gitlab!56233

Merge branch '239850-convert-stylesheets-pages-members-scss-into-page-specific-bundle' into 'master'

Convert `members.scss` into page specific bundle

See merge request gitlab-org/gitlab!56278

Add Jira Issue Note component

See merge request gitlab-org/gitlab!56068

Merge branch '300750-add-missing-reviewers-information-to-new_mention_in_merge_request_email' into 'master'

Add reviewer information to new_mention_in_merge_request_email

See merge request gitlab-org/gitlab!56184

Add stylelint cache file to .gitignore

See merge request gitlab-org/gitlab!56302

Lot of vuex duplication that can be trimmed down later

Improved award emoji picker [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!54469

Add ci pattern to migration

See merge request gitlab-org/gitlab!56185

Handle commits without descriptions for changelogs

See merge request gitlab-org/gitlab!56224

Resolve "Follow-up from "Remove safe navigation operator from Vulnerability description""

See merge request gitlab-org/gitlab!53192

Replace calls-gitaly instrumentation with  a field extension [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!55306

Migrate group iterations when using Bulk Import

See merge request gitlab-org/gitlab!56018

Update code owner approval tooltip message

See merge request gitlab-org/gitlab!55842

This changes the presenter instrumentation to a field extension, which
is simpler, easier to maintain, and will allow us to make use of the
interpreter execution engine in the future.

This also makes is easier to test resolver and types that make use of
these facilities.

Other changes:

In the current user TODOs type, ensure we take the type of the unwrapped
object If we don't do this, the presented class name will be used
instead (for types that use `present_using`). This results in incorrect
todo_type values.

The following resolvers call gitaly:

- metrics/dashboard_resolver
- last_commit_resolver
- snippets/blobs_resolver
- tree_resolver

Remove an unnecessary gitaly annotation (I was unable to verify that
this gitaly annotation was needed. So it is removed.)

This was erroneously setting constant_complexity to true for all fields
that have a resolver, since our BaseResolver sets complexity to 0 (and
`!!zero == true`).

This masks gitaly calls.