- Add a complexity of 1 if Gitaly is called at least once
 - Add an error notification if `calls_gitaly` isn't right for a
 particular field

Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at

- all commits squashed to make danger review happy

Since Redis timings appear to be increasing in production, this change
makes it easier to see what exactly which queries are being called and
where.

This is done by prepending modules in peek-redis to store the call
details.

This commit redact values for all SET commands (e.g. HMSET, GETSET,
etc.).

This new attribute is optional and used when set instead of the default
format `gitlab+deploy-token-#{id}`.

Empty usernames will be saved as null in the database.

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/50228.

Add a check for logged out user in the manual order
so that they don't see an flash message when they try to
reorder issues.

- Add two new ActiveRecord models:
  - RootNamespaceStoragestatistics will persist root namespace statistics
  - NamespaceAggregationSchedule will save information when a new update
to the namespace statistics needs to be scheduled
- Inject into UpdateProjectStatistics concern a new callback that will
call an async job to insert a new row onto NamespaceAggregationSchedule
table
- When a new row is inserted a new job is scheduled. This job will
update call an specific service to update the statistics and after that
it will delete thee aggregated scheduled row
- The RefresherServices makes heavy use of arel to build composable
queries to update Namespace::RootStorageStatistics attributes.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows

Includes changes to the Vue container registry component to support
the display of an empty message and error message when invalid
characters are found in the group, project or branch name.

repositories/index.html.haml has been changed to remove the content
and place into Vue component.

- instead of using properties
- backward compatibility has to be kept for now

- JupyterHub must not be available (installed or updated)

If an entry has been removed from the tree and later, during the same
session, a user is trying to add a new item with the same name/path we
should allow for that as long as the original entry is marked with
`deleted`.

The root_ancestor method is heavily used in EE for the group_saml
feature. Having this memoization implemented in CE would eliminate
the need of overriding the root_ancestor method in EE.

The introduction of the in-memory cache for application settings had a
side effect of making it harder to invalidate changes when the settings
occur. We now bypass the cache because it's possible the admin enabled
the usage ping, and we don't want to annoy the user again if they
already set the value.

To avoid causing significant load on the system, we add an extra check
to ensure the user is an admin. and we don't want to annoy the user
again if they already set the value. This is a bit of hack, but the
alternative would be to put in a more complex cache invalidation
step. Since this call only gets called in the uncommon situation where
the user is an admin and the only user in the instance, this shouldn't
cause too much load on the system.

The /admin panel will now always return an uncached
application setting to ensure it always has the most
current info.

Loading `ApplicationSetting` from Redis was responsible for at least 50%
of the CPU load of the Redis cluster on GitLab.com. Since these values
generally don't change very much, we can load this from the database and
cache it in memory, skipping Redis altogther. We use
`ActiveSupport::Cache::MemoryStore` as a drop-in replacement for
`RedisCacheStore` even though we probably don't need synchronized access
within `Thread.current`.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63977

i18n linting for .vue files under the
app/assets/javascripts/clusters/ directory

i18n linting for .vue files under the
app/assets/javascripts/environments directory

- enabled uninstallation
- give it a specific uninstall message
- ajust specs

i18n linting for .vue files under the
app/assets/javascripts/serverless directory

i18n linting for .vue files under the directories:
- app/assets/javascripts/error_tracking_settings
- app/assets/javascripts/filtered_search
- app/assets/javascripts/projects
- app/assets/javascripts/releases
- app/assets/javascripts/repository

This reverts commit 4bed2daef935bb4097988e0eff4830fc13a23c37.

i18n linting for .vue files under the
app/assets/javascripts/ide directory

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/46139

i18n linting for .vue files under the
app/assets/javascripts/pipelines directory

i18n linting for .vue files under the
app/assets/javascripts/pages directory

If user can update an issue under the specified confidential
issue project, should be able to find the project.

This reverts to previous behavior where we have the group only when
we don't have a project

The pipelines table was showing the loading icon
after the user cancelled or retried a pipeline.
This fixes that so the pipeline updates without
removing the table from the DOM.

All issue boards can now be collapsed via a button, re-ordered by
dragging the header, and the vertical collapsed header style was
reworked.