Consider expanding jest minimal job rule to run jest minimal job by default in all MR pipelines

Goal

See this slack thread

Currently, jest minimal job runs when ci-patterns and code-backstage-patterns are introduced in MR pipelines. We would like to expand these rules to run jest minimal by default in all MR pipelines.

There are some pros and cons discussed for running jest minimal job by default in MR pipelines:

Pros

• Decrease #master-broken investigation efforts
• Will decrease TtFF

Cons

• Increase jest failure feedback time by 15 mins (average)
• Decrease master stability (smaller degree)

Proposal

Run jest minimal job by default in all MR pipelines, with the pipeline:run-all-jest label modifier available to override.

We will still be running jest full jobs on master pipeline.