Sanitize search text to prevent XSS

See merge request gitlab/gitlabhq!3470

Require Maintainer permission on group where project is transferred to

See merge request gitlab/gitlabhq!3473

Use the '\A' and '\z' regex anchors in `InternalRedirect` to mitigate an Open Redirect issue.

See merge request gitlab/gitlabhq!3476

Pass all wiki markup formats through our Banzai pipeline filters

See merge request gitlab/gitlabhq!3479

Handle Stored XSS for Grafana URL in settings

See merge request gitlab/gitlabhq!3481

- Extend Gitlab::UrlBlocker to allow relative urls (require_absolute
  setting).  The new `require_absolute` setting defaults to true,
  which is the existing behavior.

- Extend AddressableUrlValidator to accept `require_abosolute` and
  default to the existing behavior

- Add validation for ApplicationSetting#grafana_url to validate that
  the URL does not contain XSS but can be a valid relative or absolute
  url.

- In the case of existing stored URLs, validate the stored URL does
  not contain XSS. If the stored URL contains stored XSS or is an
  otherwise invalid URL, return the default database column value.

- Add tests for Gitlab::UrlBlocker to test require_absolute setting

- Add tests for AddressableUrlValidator

- Add tests for ApplicationSetting#grafana_url

Filter out search results based on permissions to avoid bugs leaking data

See merge request gitlab/gitlabhq!3494

This will be used later for search filtering.

This is to be more consistent as there is already a :read_note policy in
NotePolicy. To keep other behaviour the same we've introduced a
Note#noteable_ability_name that is used anywhere this was expected.

Previously, when the wiki page format was anything other than `markdown`
or `asciidoc` the formatted content would be returned though a Gitaly
call. Gitaly in turn would delegate formatting to the gitlab-gollum-lib
gem, which in turn would delegate that to various gems (like RDoc for
`rdoc`) and then apply some very liberal sanitization.

It was too liberal!

This change brings our wiki content formatting in line with how we
format other markdown at GitLab, so we have a SSOT for sanitization.

https://gitlab.com/gitlab-org/gitlab/issues/30540

Fixes https://dev.gitlab.org/gitlab/gitlabhq/issues/2934 and https://gitlab.com/gitlab-org/gitlab/issues/33569

[ci skip]

[ci skip]

Fix private feature Elasticsearch leak

See merge request gitlab/gitlabhq!3451

Add spec to test different combinations.
Accept string for required_minimum_access_level
Allow more flexible project membership query

Fix broken specs : Generate new GPG key in place of expired one

Closes #32956

See merge request gitlab-org/gitlab!17853

[ci skip]

Fix Gitaly SearchBlobs flag RPC injection [Gitaly v1.59.3]

See merge request gitlab/gitlabhq!3434

Check that SAML identity linking validates the origin of the request

See merge request gitlab/gitlabhq!3377

Merge branch 'security-12717-fix-confidential-issue-assignee-visible-to-guests-12-2' into '12-2-stable'

Display only participants that user has permission to see

See merge request gitlab/gitlabhq!3402

Prevent Bypassing Email Verification using Salesforce

See merge request gitlab/gitlabhq!3406

Only render fixed number of mermaid blocks

See merge request gitlab/gitlabhq!3412

Hide disabled project milestones in project settings on group level

See merge request gitlab/gitlabhq!3415

Redirect user to root path after unsubscribing from private resource

See merge request gitlab/gitlabhq!3417

Add policy check if cross reference system notes are accessible

See merge request gitlab/gitlabhq!3427

Cancel all running CI jobs when user is blocked

See merge request gitlab/gitlabhq!3437

Filter not accessible label events

See merge request gitlab/gitlabhq!3441

Add argument to catch

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

Label events may use cross-project or cross-group references,
if the projects are not accessible by user, we don't show these
label events.