* Use a full path in Gitaly's `bin_dir` config to ensure the bundled
  Git symlink can link to the test binaries.

* Fix a regression in the `ci?` check that was introduced in
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78061.

Up to now, Gitaly has been using an external Git distribution to serve
all Git requests. This has somewhat changed with the introduction of the
`make git` target, which moved responsibility of providing a compatible
Git distribution into Gitaly. While this was a step into the right
direction, it still didn't give Gitaly full control over which Git
binaries exist and where these are located. This is proving to be
problematic in some contexts: we cannot switch between multiple Git
versions via feature flags, rollouts of new Git versions will overwrite
the old installation while Gitaly may still be running, and in general
we have no specific knowledge about which Git version we're currently
running with except for the version string.

To fix this, Gitaly has introduced a new distribution mode: instead of
pointing Gitaly's configuration at a specific Git distribution, Gitaly
can now run with in "bundled" mode. Like this, Gitaly only requires two
binaries gitaly-git and gitaly-git-remote-http which are installed into
the typicaly binary directory where all the other Gitaly-specific
binaries are installed into. Gitaly will then bootstrap a full Git
execution environment from these two binaries which is sufficient to
serve all Git requests in Gitaly.

With this in place, Gitaly has much tighter control over which Git
version is installed into what place. As a result, we can eventually
build on top of this and easily install multiple Git versions, use
feature flags and avoid issues like overwrites of the Git distribution
while an old Gitaly version is still running.

While the old configuration of pointing Gitaly at a specific Git
installation will not go away, the recommended default will at some
point become to always use the bundled Git mode. As a first test
balloon, this commit switches over the Gitaly setup helper for our Ruby
specs to use this bundled Git mode.

Add identifier to VSA summary metrics

See merge request gitlab-org/gitlab!78470

Introduce linear descendants feature flag

See merge request gitlab-org/gitlab!78542

Swap FK dast_profiles_pipelines.ci_pipeline_id to ci_pipelines for LFK

See merge request gitlab-org/gitlab!78597

Update group#shared_externally to include projects

See merge request gitlab-org/gitlab!78270

Replace usage of find/findAll in ee/spec/frontend/requirements

See merge request gitlab-org/gitlab!78644

Using CI/CD variables instead of values file to override some variables

See merge request gitlab-org/gitlab!78324

Note AWS OpenSearch as not yet supported

See merge request gitlab-org/gitlab!78478

* migrate to proper use of findComponent/findAllComponents

Add a running GDK as a requirement for frontend fixtures

See merge request gitlab-org/gitlab!78656

Replace usage of find/findAll in misc ee components (3/5)

See merge request gitlab-org/gitlab!78652

Replace GlTable with GlTableLite for vulnerabilites over time

See merge request gitlab-org/gitlab!78529

Add location of Gatsby icon to project templates

See merge request gitlab-org/gitlab!77175

Introduce Roadmap settings sidebar

See merge request gitlab-org/gitlab!78626

Move Merge Train help icon to be near merge button

See merge request gitlab-org/gitlab!78525

Changelog: other

Remove feature flag for auto-linking LFS objects in forks

See merge request gitlab-org/gitlab!78592

This change adds an identifier attribute to the VSA summary metrics.

Changelog: added

Update iteration changed notification message

See merge request gitlab-org/gitlab!78250

- Iteration period (start and due dates) should be the link/main text
- Iteration title will be made optional and should be wrapped in a
  parenthesis for display.
- Iteration cadence name should be displayed when the FF is turned on.
- Remove project iteration from notification spec.
   Project iteration has been abandoned. Iteration will always be scoped to groups.

Changelog: changed
EE: true

Introduce roadmap_settings feature flag

Remove Quarantine From Member Leaves Project Spec (User Leaves Project By URL Param)

See merge request gitlab-org/gitlab!78577

Align bot user for projects/groups term within docs

See merge request gitlab-org/gitlab!78724

Follow-up to:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77449

This commit aligns the *bot user for projects/groups* terms for all
project/group access token service accounts within the documentation.
This should clarify the type of service account as well as making the
correlation between bot users for projects and groups better
understandable.

Besides that, this commit also adds a missing chapter about group
access tokens to the token overview page and corrects the linking
within the group access token REST API page.

Update gitlab-dangerfiles to 2.8.0

See merge request gitlab-org/gitlab!78658

Change actor of context_commits flag to group

See merge request gitlab-org/gitlab!78646

Update dependency core-js to ^3.20.3

See merge request gitlab-org/gitlab!78337

Update severity level docs with latest info

See merge request gitlab-org/gitlab!78335

Reschedule migration for self-managed

See merge request gitlab-org/gitlab!78509

Reschedules migration to recalculate finding siginatures and limits it
to self-managed.

Changelog: other
EE: true

Replace deprecated usage of find/findAll in ee/spec/frontend/analytics

See merge request gitlab-org/gitlab!78631

Remove summary from Finding Evidence

See merge request gitlab-org/gitlab!77710

Lowercased runner because it's referring to agent

See merge request gitlab-org/gitlab!78725

We have guidelines for how we refer to runner vs GitLab Runner.
In this case, we mean the agent that runs the job, so it should
be lowercase. The style guide has details here:
https://docs.gitlab.com/ee/development/documentation/styleguide/word_list.html\#runner-runners

Changelog: changed

Fixed misspelling and made other edits

See merge request gitlab-org/gitlab!78716

New Actionable Insight issue template

See merge request gitlab-org/gitlab!78738