Fix max_threads for Puma with no cli_config

DB configs keys are now represented as symbols, not strings

Convert BlobHeader to Vue: Add Edit button

See merge request gitlab-org/gitlab!60986

Bust the cache for /whats-new

See merge request gitlab-org/gitlab!61081

Verify links and anchors for deeply nested urls

See merge request gitlab-org/gitlab!60115

Upgrade @gitlab/ui to v29.18.0

See merge request gitlab-org/gitlab!60926

Added introspection fragment matcher to Epic Boards

See merge request gitlab-org/gitlab!61101

Merge branch '330390-experiment-tracking-in_product_guidance_environments_webide-alert-users-to-adding' into 'master'

Set Rollout URL for in_product_guidance_environments_webide Experiment

See merge request gitlab-org/gitlab!61287

Remove unused & erroring page_title layout partial

See merge request gitlab-org/gitlab!61176

To keep feature flags organized, all flags require tracking issues to
monitor their rollout.

I forgot to add one to the in_product_guidance_environments_webide
experiment flag.

I also forgot to add the MR that introduced the flag.

Merge branch '292747-in-product-guidance-for-deployments-for-users-that-are-not-deploying-webide' into 'master'

Show an Alert that a user is not using deployments [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!57160

Enforce .git in the URL when importing Repo by URL

See merge request gitlab-org/gitlab!61115

Update injected props

See merge request gitlab-org/gitlab!61136

We want to be able to limit the amount of users who can see this alert
as a slow rollout to see if it is useful.

This experiment is only enabled for projects that don't have existing
environments, and we currently only track if the user clicks on the
Learn More link embedded in the alert.

As with all experiments, this is only applicable to GitLab.com

Provides a way to display alerts attached to files within the WebIDE.

The first alert shows guidance to users who are editing their CI
configuration about environments, if we are reasonably certain they
don't know about environments.

We need to request the parsed CI configuration while the user edits it,
and accomplish this by watching the content. This watcher is
conditionally created and destroyed when the config file is active.

The getAlert function searches through all available alerts (added
previously), returning the first alert where its show function returns
true, or null if none is found.

Actions to fetch the CI configuration for its given current
content (when it is being edited), as well as to dismiss the callout for
environment guidance are added here.

We parse the CI configuration during the mutation to only retain whether
or not we have:

- sucessfully parsed the CI config, and
- found an environment within the config.

Merge branch '329231-geo-container-registry-sync-does-not-sync-images-with-foreign-layers' into 'master'

Geo - Skip download of blobs with foreign layers

See merge request gitlab-org/gitlab!61072

Some images contains layers that might have the media type
"application/vnd.docker.image.rootfs.foreign.diff.tar.gzip"
which are not present on the registry.

In this case, the client doesn't go to the registry to fetch
the layer because it is not there but will follow the URL,
specified among other details of the layer.

Geo should not try to fetch it from the registry during sync
but skip this layer. It also does not want to follow the URL
and download it because it might violate the license.

Generalize epic filtered search component for board reuse

See merge request gitlab-org/gitlab!59706

Only send in-product emails to free groups

See merge request gitlab-org/gitlab!60906

Get extra attributes from Spamcheck response and determine verdict [RUN ALL RSPEC][RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!60915

Fix incorrect issueable counts

See merge request gitlab-org/gitlab!61230

Temporary fix until we figure out how to work with BootstrapVue sort
keys.

Ensures that the initial sort parameter is consistent with what's
computed on user interactions. This ensures that we don't unnecessarily
re-trigger a GraphQL mutation when sorting by creation date, descending.

Add migration to update subscription plans

See merge request gitlab-org/gitlab!55625

Support new gitlab-license gem version

See merge request gitlab-org/gitlab!61009

Add CountBoardsMetric

See merge request gitlab-org/gitlab!60022

Add offset and limit parameters to names resolver

See merge request gitlab-org/gitlab!61061

Using a query param to bust the cache on requests to /whats-new. While I
haven't personally experienced a cacheing issue, it has been reported
that the count and notification bubble are correct, though when loading
the "What's New" module, the content is stale.

Initially I combed over the cache headers, thinking maybe something was
missed there, but the headers seem correct. And given I can't reproduce
the experience, this issue is difficult to solve.

I chose this simple approach to see if it solves the issue, though I'm
open to other solutions.

part of:
https://gitlab.com/gitlab-org/gitlab/-/issues/325899