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

[RUN AS-IF-FOSS] Add SLA to incident list

See merge request gitlab-org/gitlab!44957

Fix label `x` button showing for unauthorized users

See merge request gitlab-org/gitlab!45189

Integrate usage statistics with new API

See merge request gitlab-org/gitlab!44945

RuboCop: Add cop for GraphQL::ID_TYPE

See merge request gitlab-org/gitlab!44831

Fix download test coverage inject

See merge request gitlab-org/gitlab!45235

Add feature categories to web metrics and logs

See merge request gitlab-org/gitlab!44918

Step 1/3: Add GraphQL query to fetch single release

See merge request gitlab-org/gitlab!44766

Resolve "View burnup chart in the Iteration report"

See merge request gitlab-org/gitlab!44667

Allow passing either milestone to iteration to query

This won't be present in API logs yet because API endpoints don't yet
have feature categories.

As this counter is implemented in a Rack middleware, the easiest way to
exfiltrate the category is just to add it to a header.

Revert "Merge branch 'sh-update-rack-2.1.4' into 'master'"

See merge request gitlab-org/gitlab!45246

Fix border hover for incidents and alerts

See merge request gitlab-org/gitlab!45117

Replace fa-calendar icons with GitLab SVG calendar icon

See merge request gitlab-org/gitlab!45175

Convert Props to Injected Values for Feature Flags

See merge request gitlab-org/gitlab!45033

Remove duplicated BS display properties from Issuables

See merge request gitlab-org/gitlab!45177

DAST scans site profile: Fix inprogress transition

See merge request gitlab-org/gitlab!44865

This reverts merge request !44518

Wiki UI improvement: Move Wiki title below actions bar

See merge request gitlab-org/gitlab!44390

To look more like issues/mrs

Improve requests/api/project_snippets_spec performance

See merge request gitlab-org/gitlab!45127

- Replaces the Fontawesome calendar icon
with the GitLab calendar SVG

Added multiple methods(webhook, scm, issue boards)

See merge request gitlab-org/gitlab!45237

Indicate on signin page instance is self-managed

See merge request gitlab-org/gitlab!44681

This MR updates the usage quotas page to
consume data coming in from updated GraphQL API
responses

Refactor DAST Site Profile Form

See merge request gitlab-org/gitlab!44997

Skip Bootrap popover initialization

See merge request gitlab-org/gitlab!45216

Hide issues badge when there are no issues

See merge request gitlab-org/gitlab!44663

Update rouge to v3.24.0

See merge request gitlab-org/gitlab!45225

Consolidate the Edit and Web IDE buttons

See merge request gitlab-org/gitlab!44311

Enable core_security_mr_widget feature flag by default

See merge request gitlab-org/gitlab!44764