Implement mechanism to skip/quarantine jest specs in vue 3

What does this MR do and why?

Implement mechanism to skip/quarantine jest specs in vue 3

Some of the jest specs are failing spectacularly with Vue 3 by just ending in a locked up state.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

N/A

How to set up and validate locally

1. VUE_VERSION=3 yarn jest $(git grep -l describeSkipVue3)

assigned to @leipert

added pipelinetier-1 label

requested review from @markrian

changed the description

removed review request for @markrian

added maintenancetest-gap vue3-migration labels

added typemaintenance label

added frontend label

	1 Warning
	This merge request changed files with disabled eslint rules. Please consider fixing them.

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Disabled eslint rules

The following files have disabled eslint rules. Please consider fixing them:

• spec/frontend/__helpers__/vue3_conditional.js

Run the following command for more details

node_modules/.bin/eslint --report-unused-disable-directives --no-inline-config \
  'spec/frontend/__helpers__/vue3_conditional.js'

Reviewer roulette

Category	Reviewer	Maintainer
frontend	@agulina (UTC+2, same timezone as author)	@sheldonled (UTC+1, 1 hour behind author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

@leipert Somehow you assigned me then unassigned me. So I'll reassign myself again

requested review from @markrian

changed milestone to %17.3

changed the description

resolved all threads

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 label and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.