Loosen jenkins-bot approval requirements

Created by: DemianX0

I was trying to create a demo for https://gerrit.wikimedia.org/r/c/mediawiki/skins/Vector/+/592325

The previous patch in chain fails the build, I can't do anything about that.

Demo creation failed because of this:

Querying patch metadata... https://gerrit.wikimedia.org/r/changes/?q=change:592325&o=LABELS&o=CURRENT_REVISION https://gerrit.wikimedia.org/r/changes/mediawiki%2Fskins%2FVector~master~I182eedeff0b6eb62250f2682b89f30c8ff0f70de/revisions/ae3b99d9a3c4a1708936eda50ef883e4eb3c3c60/related https://gerrit.wikimedia.org/r/changes/592325/revisions/5/commit https://gerrit.wikimedia.org/r/changes/584694/revisions/25/commit https://gerrit.wikimedia.org/r/changes/?q=change:I8e153c0ab927f9d880a68fb9efb0bf37b91d26b2&o=LABELS&o=CURRENT_REVISION Patch must be approved (Verified+2) by jenkins-bot

I'm solving this by squashing the two patches, however that's not optimal as now the patch is not useful to present the changes I've applied.

Optional: Futhermore, it would be helpful to have an option to create a demo with an unapproved patch. jenkinsbot does certain strict tests that are necessary to pass for live code, but not for demonstration code. Sometimes it's not worth the time it takes to investigate and fix every issue jenkins reports.