Support editing and deleting of dismissal comments

See merge request gitlab-org/gitlab-ee!11963

This change supports the editing and deleting of vulnerability feedback
dismissal comments. It also supports adding a comment if one was not
supplied during the initial dismissal. For the backend this is all done
through the update action of the vulnerability feedback controller.

Resolve EE-specific import in board_spec.js

Closes #10716

See merge request gitlab-org/gitlab-ee!13939

Fix warning in spec from committing unused mutation

See merge request gitlab-org/gitlab-ce!28815

Fix MR checkboxes alignment on mobile

Closes #57037

See merge request gitlab-org/gitlab-ce!28845

Extract toggleFilter() into issue boards store

See merge request gitlab-org/gitlab-ce!29083

i18i EE JS files in directories starting with s

See merge request gitlab-org/gitlab-ee!13491

This is one of many MRs opened in order to improve the overall
internationalisation of the GitLab codebase.

This commit only targets Vanilla JS files.

i18n documentation
https://docs.gitlab.com/ee/development/i18n/externalization.html

Adjustments related to DiffNotes on diffs outside of a project's main repository

See merge request gitlab-org/gitlab-ce!29023

Modify `DiffNote` to reuse it for Designs

See merge request gitlab-org/gitlab-ee!13703

Fix locale/gitlab.pot failure

See merge request gitlab-org/gitlab-ee!13951

Update rendering of merge request in merge request widget

Closes #40246

See merge request gitlab-org/gitlab-ce!28238

EE port of mr-widget-merge-error

See merge request gitlab-org/gitlab-ee!13496

Increase height of move issue dropdown

See merge request gitlab-org/gitlab-ce!29087

Fix all EE `no-implicit-coercion` ESLint violations

See merge request gitlab-org/gitlab-ee!13803

This modifies the `DiffNote` model so we can create `DiffNote`s for
`DesignManagement::Design`s.

It also includes some specs illustrating how the
`Notes::CreateService` will need to be used from GraphQL for designs

This commit is the result of running `yarn eslint --fix` after enabling
the `no-implicit-coercion` ESLint rule.  This rule has been added to
our ESLint config here:

https://gitlab.com/gitlab-org/gitlab-eslint-config/merge_requests/14

Expose wiki_size on GraphQL API

See merge request gitlab-org/gitlab-ce!29123

Adds issue template for feature flag roll out

See merge request gitlab-org/gitlab-ce!28751

Remove "Module" from vulnerability feedback module name

See merge request gitlab-org/gitlab-ee!13935

Remove `approval_rules` feature flag and remove obsolete approvals implementation

See merge request gitlab-org/gitlab-ce!28979

Remove `approval_rules` feature flag and remove obsolete approvals implementation

Closes #10685

See merge request gitlab-org/gitlab-ee!12436

Update maven.gitlab-ci.yml for GitLab Package

See merge request gitlab-org/gitlab-ce!28796

Combine Running Gitaly on its own server details

See merge request gitlab-org/gitlab-ce!29094

Cancel auto merge when merge request is closed

See merge request gitlab-org/gitlab-ce!28782

Resolve "Use GitLab serverless with existing Knative installation"

Closes #58941

See merge request gitlab-org/gitlab-ce!27173

Port of Use GitLab serverless with existing Knative installation to EE

See merge request gitlab-org/gitlab-ee!11589

Remove Kn services cache from Clusters::Application::Knative

Knative function can exist even if user did not installed Knative via
GitLab managed apps.

-> Move responsibility of finding services into the Cluster
-> Responsability is inside Clusters::Cluster::KnativeServiceFinder
-> Projects::Serverless::FunctionsFinder now calls depends solely on a
cluster to find the Kn services.
-> Detect Knative by resource presence instead of service presence
-> Mock knative_installed response temporarily for frontend to develop

Display loader while `installed === 'checking'`

Added frontend work to determine if Knative is installed

Memoize with_reactive_cache(*args, &block) to avoid race conditions

When calling with_reactive_cache more than once, it's possible that the
second call will already have the value populated. Therefore, in cases
where we need the sequential calls to have consistent results, we'd fall
under a race condition.

Check knative installation via Knative resource presence

Only load pods if Knative is discovered

Always return a response in FunctionsController#index

- Always indicate if Knative is installed, not installed or checking
- Always indicate the partial response for functions. Final response is
guaranteed when knative_installed is either true | false.

Adds specs for Clusters::Cluster#knative_services_finder

Fix method name when calling on specs

Add an explicit check for functions

Added an explicit check to see if there are any functions available

Fix Serverless feature spec

- we don't find knative installation via database anymore,
rather via Knative resource

Display error message for request timeouts

Display an error message if the request times out

Adds feature specs for when functions exist

Remove a test purposed hardcoded flag

Add ability to partially load functions

Added the ability to partially load functions on the frontend

Add frontend unit tests

Added tests for the new frontend additions

Generate new translations

Generated new frontend translations

Address review comments

Cleaned up the frontend unit test.
Added computed prop for `isInstalled`.

Move string to constant

Simplify nil to array conversion

Put knative_installed states in a frozen hash for better read

Pluralize list of Knative states

Quey services and pods filtering name

This way we don't need to filter the namespace in memory.
Also, the data we get from the network is much smaller.

Simplify cache_key and fix bug

- Simplifies the cache_key by removing namespace duplicate
- Fixes a bug with reactive_cache memoization