Block features based on issue type. Allows certain UI elements, quick
actions and other features to be filtered for issue types.

- Specs for EE and CE

The changes tested here are to see if in EE projects in the same groups
count as part of the same relative positioning set. We do not need to
test every method - just the scoping query.

Frankly a bunch of the movement tests could also be removed, but they
are all calling public methods so it is fine for them to test the
interface.

As part of making simple related issues free

Create a resource_iteration_event record when iteration changes
on issues or merge_request.

This reverts commit a5923aa6, which
reverted the relative_positioning improvements.

This reverts merge request !37724

This expands the usable range of positions to the negative numbers,
uses more precisely chosen gap sizes, and deals more effectively with
edge cases.

Allow to order issues by the number of other
issues they are blocking.

* added resolver spec
* minor fixes in the board list servicer and resolver
* added input arguments for issue filtering
* updated the query to get epics

Persist blocking issues count on database.
This will avoid slow queries when ordering issues by blocking counts.

Filtering iterations by ID, and display just info
No edit view for now

Moves models/api code related to service desk
into core tier.
Part of https://gitlab.com/gitlab-org/gitlab/-/issues/215364.

Adds two new status page-related attributes
to usage ping, representing counts of when
publish and unpublish actions are taken.

Also refines status_page_issues usage ping
attribute to only reflect projects which
has status page enabled, as it did previously.

Adds Epics select dropdown in New Issue page to directly
assign newly created issue to an Epic.

Add count of all alerts to usage ping and add a second
metric for manually created alerts

The plan for RSpec 4.0 is to disable monkey patching:
https://rspec.info/blog/2013/07/the-plan-for-rspec-3/#zero-monkey-patching-mode

This commit stops using RSpec monkey patching:
https://relishapp.com/rspec/rspec-core/docs/configuration/zero-monkey-patching-mode

To have idempotent publishing jobs for publishing a project's
issues to the status page, issues are pushed based on the
confidential state of an issue. This commit swaps over to the
publishing an issue only if a StatusPage::PublishedIncident
exists for the issue. This allows finer control over to the user
on whether an issue should be published to the status page.

This change is part of
https://gitlab.com/gitlab-org/gitlab/-/issues/212566 to move all Design
Management code to FOSS.

This MR moves some specs to FOSS that had previously been missed.

Also extended specs

This change is part of
https://gitlab.com/gitlab-org/gitlab/-/issues/212566 to move all Design
Management code to FOSS.

This MR moves:

- Models
- Factories
- Design repository-related code

The repository-related code has been included because the models and
model specs rely on design repositories to be working.

To support an ability to publish status page issues
at a user's discretion, we want to store whether an
issue has been published. This adds a table and model
to represent a published incident.

Change whitespace to allow for shorter lines
to increase readability

It adds confidentiality attribute to Epic model and also
adds validations which assure that confidential epic
can have only confidential issues.

- calculate epic health status based on issues

Used on vue notes-app to iterate over blocking issues

Allows service desk emails to be received at the new moved issue.

This method exists to cause changes to the index to appear in specs.
In https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24298/diffs we
will be changing how changes are processed, and it will be valuable to
have a separate method in specs that we can hook into.

We're changing the way indexing works, currently we pass
changed_fields to ElasticIndexerWorker for notes update taking
storage and harming job deduplication. We're replacing
that logic with a separate jobs per each changed note.

Take into account also issues which reference another issue
with link type `blocked_by`.

Also issue visibility is now not taken into account - `blocked` status
is displayed to all users no matter if they can access blocking issue
or not.