- Replace Boostrap dropdown with GlDropdown for comment submit button.

- Remove note_dropdown qa selector

- Update the shared example Thread Comments
The shared examples under "Thread Comments" have split into two:
"Thread Comments for commit and snippet"
and "Thread Comments for issue, epic and merge request"

Why?
After we've replaced Bootstrap dropdown button
with GitLab UI counterpart in comment_form.vue,
issue, epic and merge request uses GitLab UI GlDropdown
that has slightly different selectors.

Previously quarantined examples have been restored in this commit:
https://gitlab.com/gitlab-org/gitlab/-/issues/196825

Clarify stop job required keywords as it relates to rules

See merge request gitlab-org/gitlab!52439

Fix selected item not being highlighted in the new group boards

See merge request gitlab-org/gitlab!53113

Because board_card.vue component will be removed in the future
and is not used in the new boards that uses graphql,
we are renaming it to `board_card_deprecated.vue`.

Cross link between code coverage topics

See merge request gitlab-org/gitlab!54770

Update path to AutoDevops admin settings in docs

See merge request gitlab-org/gitlab!54768

Add creator to custom emoji

See merge request gitlab-org/gitlab!53879

Add dotnet coverage example

See merge request gitlab-org/gitlab!54057

Add ruby to documentation as supported language in SAST

See merge request gitlab-org/gitlab!54728

Docs: Fix customers link

See merge request gitlab-org/gitlab!54722

Reset templates cache key

See merge request gitlab-org/gitlab!54614

It may have moved at some point without updating the docs; it's findable
as is (with some guesswork) but this makes it clearer

Update Gitaly version

See merge request gitlab-org/gitlab!54761

Update Gitaly version

See merge request gitlab-org/gitlab!54759

Un-quarantine export project e2e test on staging

See merge request gitlab-org/gitlab!54659

Return only supported issue types for selected Jira Project

See merge request gitlab-org/gitlab!53705

This change improves the way we fetch available issue types for Jira.
From now we will fetch only these types that are available in the
workflow for given project instead of loading all possible issue types
from the system.

External link fixes for docs

See merge request gitlab-org/gitlab!54741

Send SIGINT instead of SIGQUIT to puma

See merge request gitlab-org/gitlab!54446

Fix Metric tab not showing up on operations page

See merge request gitlab-org/gitlab!54736

Apply new GitLab UI for request email button

See merge request gitlab-org/gitlab!53966

Rename indexes on GitLab.com

See merge request gitlab-org/gitlab!51011

Puma does not handle SIGQUIT [1], so worker processes will not get
terminated when calling /etc/init.d/gitlab stop

[1] https://github.com/puma/puma/blob/master/docs/signals.md

- fix broken test
- add additional test

Increase specificity of StandardContext environment

See merge request gitlab-org/gitlab!54511

They were being labelled as development

Add description field to cluster agent token

See merge request gitlab-org/gitlab!54091

Added description field to Clusters::AgentToken
Updated GraphQL mutation and create service to suport new field
Updated associated tests and docs

Releases::CreateEvidenceWorker is not a cronjob

See merge request gitlab-org/gitlab!54432

This was accidentally added in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/47638/

Change method name for fetching issue and merge request templates
which also resets the caching key. Also do not cache empty hash
on fallback but rather default to nil, which would make another
gitally request and cache a success value or be nil in case of failure

Fix License Compliance widget button spacing

See merge request gitlab-org/gitlab!54701