Add regex switch expression tool

[npinter]

As discussed here galaxyproject/galaxy#20966 I added the regex switch module as an expression tool.

Workflow example:

Workflow route 1:

Workflow route 2:

@mvdbeek mentioned there is a Galaxy bug regarding the workflow invocation. Tool works but "Attempting to schedule workflow invocation" takes 5 min to pipe the boolean to the target tools.

FOR CONTRIBUTOR:

• I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
• License permits unrestricted use (educational + commercial)
• This PR adds a new tool or tool collection
• This PR updates an existing tool or tool collection
• This PR does something else (explain below)

[npinter]

Other regex tools and other expression tools are located in the category "Text Manipulation", so I changed "Expression tools" to that.

[npinter]

I don't see why it fails..

[npinter]

Is it because the tool doesn't generate a real output (only booleans?)? @mvdbeek

[bernt-matthias]

Guess "element name" needs better explanation. I guess you assume that the tool is mapped over a collection.

[npinter]

It's the name of the dict element (job["input"]["name"]) of cwl (?), which looks like that:

    "engineConfig": [],
    "job": {
        "input": {
            "file_ext": "tabular",
            "file_size": 14,
            "name": "table.tsv",
            "metadata": {
                "dbkey": "?",
                "data_lines": 2,
                "comment_lines": 0,
                "columns": 2,
                "column_types": [
                    "int",
                    "int"
                ],
                "column_names": [],
                "delimiter": "__tc__"
            },
            "src": {
                "src": "hda",
                "id": 4
            }
        },
        "pattern": "\.csv$"
    },
    "context": null,
    "outdir": null,
    "tmpdir": null,

Not sure if this name comes either of the element identifier or the element name (I guessed the latter).

[npinter]

@bernt-matthias any idea why the testing fails?

[npinter]

@bernt-matthias looks like tests are green now :)

[bernt-matthias]

Should we add a empty_field validator instead to the param?

[npinter]

Thanks! Added!

[npinter]

Testing fails again with the same cryptic error as before (..which turned green at some point :) )

[bernt-matthias]

Let me use the opportunity to debug the failure. I guess the problem is due to #7293

[bernt-matthias]

Fix is coming #7348 (I hope)

[npinter]

sorry for bump, but looks like it worked :) thank you @bernt-matthias