Recognise links to urls in job logs

See merge request gitlab-org/gitlab!40175

Credit goes to: @mrincon

Docs: Added disable shared runners for group

See merge request gitlab-org/gitlab!44315

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/23123

Enable usage_data_api feature flag by default

See merge request gitlab-org/gitlab!45004

Add null guard for rootStorageStatistics

See merge request gitlab-org/gitlab!45270

Merge branch '258980-enable-feature-flag-by-default-of-admin-approval-for-new-user-signups' into 'master'

Resolve "[Feature flag] Enable `admin_approval_for_new_user_signups` by default"

See merge request gitlab-org/gitlab!45233

Update credentials inventory docs

See merge request gitlab-org/gitlab!45133

Updates credentials inventory docs with a
delete SSK key section.

Add purchase storage button to storage banners

See merge request gitlab-org/gitlab!45159

Add a button to purchase storage to the new version of the storage
banners.

Migrate tasks by type dropdown divider

See merge request gitlab-org/gitlab!44652

Update snapshots and tests in light of
using dropdown-header instead of list-item

Resolve "Provide optional title and description before submitting edits made with the Static Site Editor"

See merge request gitlab-org/gitlab!44512

Added modal and controls components for
overall editing merge request metadata

Move CI header CSS to utility classes

See merge request gitlab-org/gitlab!44901

Add development guidelines for wikis

See merge request gitlab-org/gitlab!43558

Adds a new page in `doc/development`, along with some tweaks to our
Vale grammar checker.

Replacing vue shared tooltip on calendar icon

See merge request gitlab-org/gitlab!45059

docs/ci/predefined_variables: fix variable name in example

See merge request gitlab-org/gitlab!45131

Update Gitaly version

See merge request gitlab-org/gitlab!45272

Add Incident SLA docs

See merge request gitlab-org/gitlab!44879

The page needed restructuring, and some of the images needed to be
either renamed (and used somewhere else) or deleted. This commit
handles only the images; the linking text will be handled in a
separate commit.

[Group Migration MVC] Store temporary data used for a GitLab import

See merge request gitlab-org/gitlab!42978

Rename ForwardDeploymentWorker to DropOlderDeploymentsWorker

See merge request gitlab-org/gitlab!44862

This change enables the feature flag
`admin_approval_for_new_user_signups `
by default

Add docs for: `Optional admin approval for local user sign up` feature

See merge request gitlab-org/gitlab!44963

This change removes the feature flag
`Remove feature flag ‘admin_approval_for_new_user_signups’`

Add Delete buttons to the SSH tab of the credential inventory

See merge request gitlab-org/gitlab!41592

This adds a delete button to the credentials
inventory display for admins and groups.

Add classes to check excess storage size

See merge request gitlab-org/gitlab!45155

Add classes to calculate and check the excess storage size of a
namespace/group.

This happens when there is no rootStorageStatistics
gathered for the namespace. Then we intentionally return null.

We want to start importing Group and Project data directly from
another GitLab instance, via the API. To do this, we need somewhere
to store a mapping between the source entity and the destination
entity.

Create the Entity model which is associated with a BulkImport,
and used to store the data required to link the entity (project or
group) on the source instance and the destination instance.

This model introduces:

1. `bulk_import_id` -> the bulk import that this data belongs to.
2. `parent_id` -> the parent ImportEntity that this one should be
   imported into
3. `source_type` -> what kind of entity this is (group or project)
4. `source_full_path` -> path to access the entity on the source
5. `destination_name` -> what to call the entity on the when it's
   created
6. `destination_namespace` -> where to store the entity on the
   destination.
7. `status` -> for use with the state machine to determine the import
   status of this entity
8. `jid` -> the job ID of the sidekiq job that will/has processed this
   import.

This is a component of the Group Migration MVC epic:
https://gitlab.com/groups/gitlab-org/-/epics/4374

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42978
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/250280

We want to start importing Group and Project data directly from
another GitLab instance, via the API. To do this, we need somewhere
to store authentication data so that we can execute the import in
background jobs.

Create the BulkImport::Configuration model which is associated with
a BulkImport, and used to store the authentication data for the
source GitLab instance. This will be followed up by the
introduction of the other models the store the import data.

This model introduces:

1. `bulk_import_id` -> the bulk import that this configuration
   applies to.
2. `api_url` -> the domain for the source instance.
3. `access_token` -> the personal access token of the user on the
   source instance for authentication.

This is a component of the Group Migration MVC epic:
https://gitlab.com/groups/gitlab-org/-/epics/4374

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42978
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/250280

We want to start importing Group and Project data directly from
another GitLab instance, via the API. To do this, we need somewhere
to store authentication data, entity mapping data and other metadata
so that we can perform the import in background jobs.

Create the BulkImport model which is associated with a user, and used to
group together all the data relating to the one bulk import request from
the user. This will be followed up by the introduction of the other
models the store the import data.

This model introduces:

1. `source_type` -> where the data for this import is being sourced
   from. For now this will just be GitLab imports, but in the future we
   could expand this structure to other services like GitHub and
   Bitbucket.
2. `user_id` -> the user that initiated the import.
3. `status` -> to be used by the state machine for recording the status
   of the overall import.

This is a component of the Group Migration MVC epic:
https://gitlab.com/groups/gitlab-org/-/epics/4374

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42978
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/250280

Update split button styling

See merge request gitlab-org/gitlab!44399

Mention Jira IDs must be uppercase

See merge request gitlab-org/gitlab!45107