The customers app requires a last name for the creation of the customer
record. As the new purchase flow does not currently have a way for users
to set a last name, fallback to the old flow when the user does not have
a last name set. This was causing issues with users in the following
state:

  1. User does not have a last name (signed up before we split the name
     field) and their full name only has one word
  2. User does not have an existing customers dot account
  3. User is creating the subscription on .com
  4. User is creating the subscription for a group (ie, using the
     purchase flow that does not redirect to customers-dot)

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/298721

Update Gitaly version

See merge request gitlab-org/gitlab!51721

Removes the mr_commit_neighbor_nav feature flag

See merge request gitlab-org/gitlab!51477

Merge branch '294422-follow-up-from-fire-webhook-when-updating-or-removing-a-group-member' into 'master'

Send email when group member expiration date is updated

See merge request gitlab-org/gitlab!50310

Doesn't work yet

Extend diffs_metadata.json w/project & user names

See merge request gitlab-org/gitlab!50666

Update dependency @gitlab/ui to v25.11.1

See merge request gitlab-org/gitlab!51619

Default enable set_user_availability_status

See merge request gitlab-org/gitlab!51668

Default enables the feature flag and
updates related documentation

Alert on transfer error in admin project controller

See merge request gitlab-org/gitlab!50541

Update Gitaly version

See merge request gitlab-org/gitlab!51715

Remove feature flags from artifacts destroy services

See merge request gitlab-org/gitlab!51323

Remove margin-top: 0 for snippets empty state

See merge request gitlab-org/gitlab!51038

Correct status indicator for job groups when failure is allowed

See merge request gitlab-org/gitlab!51478

Add `/reassign_reviewer` command

See merge request gitlab-org/gitlab!47606

* Based more or less on the /reassign command for issues and MRs

Resolve "Track comment related metrics for a merge request"

See merge request gitlab-org/gitlab!51521

Remove DOMContentLoaded Eventlistener from Performance Bar index

See merge request gitlab-org/gitlab!51204

Allow removing iterations in Issues::Updateservice

See merge request gitlab-org/gitlab!51179

Update Gitaly version

See merge request gitlab-org/gitlab!51703

Fixed broken link

See merge request gitlab-org/gitlab!51533

Fix slack application helper card

See merge request gitlab-org/gitlab!51034

Remove vue/order-in-components override

See merge request gitlab-org/gitlab!51383

The rule override was in place to make the transition to the latest
`vue/recommended` ruleset easier, i.e., tackled iteratively.

Now that most violations of this rule have been fixed, this override can
be removed, so that we adopt the stricter version from
`vue/recommended`.

Part of https://gitlab.com/gitlab-org/gitlab/-/issues/297216.

Refactor/Reorganize api.js for better tree-shaking

See merge request gitlab-org/gitlab!50038

Creates new API directory with split files

This splits out all User related API calls to better
tree-shake the big file

Updated the user merge requests + status modal

Refactored + Organized projects API calls

Fixed specs for api tree shaking

Centralized api.js with named exports

Changed to a central rest_api file

Restructured to rest_api import

Needed Prettier Update

Fixed spyOn for UserApi

Remove ci_slow_artifacts_removal
Remove ci_split_pipeline_artifacts_removal
Log how many job artifacts are removed on each execution

Mention ConventionalComments browser addon

See merge request gitlab-org/gitlab!51086

Speed up pull mirroring by asking Gitaly if tags have changed

See merge request gitlab-org/gitlab!49629

Currently, pull mirroring will fetch the full list of tags for a
repository twice - before and after the pull - and use the diff between
them to work out which new tags have been added.

This seems unavoidable with the current output of `git fetch`, but we
*can* skip doing the second call (and cache invalidation) if there have
been no tag changes. This is the common, happy path, so should be worth
implementing.

Add .terraform.lock.hcl to terraform template in order to support terraform 0.14

See merge request gitlab-org/gitlab!50647

Patch from https://gitlab.com/gitlab-org/gitlab/-/issues/243857#proposalSigned-off-by: sirlatrom <sune.keller@gmail.com>