This connects the GraphQL queries to display
the authentication logs as well as adds
empty states

We have a `Default project creation protection` setting in
`Admin -> Settings -> General -> Visibility and access controls` that
controls the default setting for the group for the minimum access needed
to create a project in the group. We have a `No one` option that
prevents even the admins from creating projects in the group. Therefore,
we have added a new option `Administrators` for this setting, allowing
admins to create projects in the group by default.

With this new option selected, when admin mode is enabled, the admin
will need to enter admin mode to create new projects.

Changelog: added

Move CSS Classes `tab-width-X` from `utilities.scss` to `app/assets/stylesheets/framework/layout.scss`

- Removes duo free access banner feature flag
- Removes associated functionality
- Removes deprecated specs

Changelog: removed

Changelog: changed

- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/170569

Changelog: other

Changelog: changed

Rename _old_repository_size_limit_setting.html.haml to
repository_size_limit_setting_for_group.html.haml.
Having old in the name could imply that this would be
removed, which isn't the case. This file is used
so admins can override repository_size_limit for groups.

## What does this MR

It updates workers data consistency from `:always` to `:sticky` for workers maintained by `permissions`,
as a way to reduce database reads on the primary DB. Check https://gitlab.com/gitlab-org/gitlab/-/issues/462611.

To reduce resource saturation on the primary node, all workers should be changed to `sticky`, at minimum.

Since jobs are now enqueued along with the current database LSN, the replica (for `:sticky` or `:delayed`)
is guaranteed to be caught up to that point, or the job will be retried, or use the primary. Consider updating
the worker(s) to `delayed`, if it's applicable.

You can read more about the Sidekiq Workers `data_consistency` in
https://docs.gitlab.com/ee/development/sidekiq/worker_attributes.html#job-data-consistency-strategies.

You can use this [dashboard](https://log.gprd.gitlab.net/app/r/s/iyIUV) to monitor the worker query activity on
primary vs. replicas.

Currently, the `gitlab-housekeeper` is not always capable of updating all references, so you must check the diff
and pipeline failures to confirm if there are any issues.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::UpdateWorkersDataConsistency keep.

To provide feedback on your experience with `gitlab-housekeeper` please create an issue with the
label ~"GitLab Housekeeper" and consider pinging the author of this keep.

Changelog: other

# Conflicts:
#	.rubocop_todo/sidekiq_load_balancing/worker_data_consistency.yml

# Conflicts:
#	.rubocop_todo/sidekiq_load_balancing/worker_data_consistency.yml

    Updates the user finder to find or create import source users, updates stage
    workers, and adds a new class to handle pushing placeholder references.

    Changelog: added

Upgrades ESLint from v8 to v9.13.0. Among other things, this requires
monkey-patching the `@graphql-eslint/eslint-plugin` package which does
not support ESLint 9 in v3, and we can't upgrade to v4 just yet.

Changelog: other

Changelog: fixed

This will store cached rolled up weight values for work items

Changelog: other

Changelog: added

# Conflicts:
#	app/assets/javascripts/ml/model_registry/constants.js

Adds stories with:
- the tooltip available
- with useLink = false

This handles the award emojis assigned to the original work item
being copied to the work item in the new destination.

This also changes the copying of assignees to happen in bulk
rather than one item at a time.

re https://gitlab.com/gitlab-org/gitlab/-/issues/339766

Changelog: changed

When there is only 1 board in a group or project, allow users with
appropriate permission to delete it, and warn them in the "Are you
sure?" modal about what will happen.

Changelog: changed

Changelog: changed

A few slight copy, layout and style adjustments

Changelog: changed

`new_profile_two_factor_auth_path` doesn't exists and it should be
`profile_two_factor_auth_path` instead.

Changelog: fixed

Completing various UX polish issues for pipeline authoring

Changelog: changed

Changelog: fixed

When a work item has email participants
every public comment will send Service Desk
emails to external participants.

On regular issues
we display a warning that the email participants
will receive notifications and we now also do that
on work items.

Update graphql docs
Add origin_project_full_path

Changelog: added

As per the [Organization blueprint](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/organization/#roles-and-permissions),
we should ensure that only organization owners have access to
Organization > Users and regular organization users should not have
access to this page.

Changelog: other

Resets calendar color to current
rather than default in order to match
other nearby icons.

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/170893

Fixes the todo counts query name in the `updateCounts` to ensure counts
are properly re-fetched when marking all todos as done.

Co-authored-by: Fiona Neill <fneill@gitlab.com>

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/423509

**Problem**

The logic to convert repository size limit is defined on controller
level and service level. It leads to a double convertion problem.
Controller converts megabytes to bytes and then service repeats the
process.

However, it's broken only for create group flow. Because the update
group doesn't use a service.

**Solution**

* Use `Groups::UpdateService` to update groups from Admin area
* Remove byte convertion logic from controller

Changelog: fixed
EE: true