Allow more special characters for test names seen in production

* Allow more special characters including the colon (the `openqa-clone-job`
  script will have to cope with it by only splitting the key/testname on
  the first colon)
* Keep `=` and tabs disallowed; the production jobs using those characters
  are most likely created by accident
* See https://progress.opensuse.org/issues/177267

lib/OpenQA/Jobs/Constants.pm

@@ -7,7 +7,9 @@ use Mojo::Base -base, -signatures;
 use Exporter 'import';
 
 # define regex for validating test names in accordance with `JobScenarios-01.yaml` and `JobTemplates-01.yaml`
-use constant TEST_NAME_REGEX => qr/^[A-Za-z 0-9_*.+-]+$/;
+# note: In contrast to the YAML schema a few more characters are allowed here as they are useful for manually
+#       triggered jobs, e.g. via `openqa-clone-custom-git-refspec`.
+use constant TEST_NAME_REGEX => qr|^[A-Za-z 0-9_*.+,:/#@%"'-]+$|;
 
 # job states
 use constant {

t/api/04-jobs.t

@@ -826,8 +826,8 @@ subtest 'get job status' => sub {
 };
 
 subtest 'validation of test name' => sub {
-    my @disallowed = ('spam@eggs', 'spam:eggs', "spam\teggs");
-    my @allowed = ('spam.eggs', 'spam+eggs', 'spam eggs');
+    my @disallowed = ('spam=eggs', "spam\teggs");
+    my @allowed = ('spam.eggs', 'spam+eggs', 'spam:"eggs"', 'spam@eggs', "spam 'eggs'");
     $t->post_ok('/api/v1/jobs', form => {TEST => $_})->status_is(400, "test name $_ disallowed") for @disallowed;
     $t->json_is('/error' => 'The following settings are invalid: TEST', 'error for invalid test name returned');
     $t->post_ok('/api/v1/jobs', form => {TEST => $_})->status_is(200, "test name $_ allowed") for @allowed;