Implement regex validators for text workflow parameter

[mvdbeek]

Can't quite get the repeat to render in the editor when loading the persisted state ... but other than that I think this is functional. Will also need galaxyproject/gxformat2#105 for tests

How to test the changes?

(Select all options that apply)

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.
• Instructions for manual testing are as follows:
  1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[jmchilton]

Probably is worth aligning the user facing language here with the rule builder. I used "regular expression" instead of regex throughout the frontend pieces. I think that is the right call in terms of clarify but it isn't a hill I am going to die on. I would just switch around the rule builder if you go with regex. I guess both components should be ported to use the new help terms also so we have a unified... "check out how to learn about regular expressions" blurb.

[bgruening]

xref: galaxyproject/training-material#5288 (comment)

(maybe we can add regular expression to John's new help infrastructure and link to GTN?)

[mvdbeek]

regular expression sounds good to me, but we're using the tool form builder here (for better or worse), do you see a way to embed terms here ? to the form builder this just looks like a regular text parameter.

[mvdbeek]

Maybe it's time to have a regex parameter, where we can provide more help ? That concept could be extended to awk, ecmascript, python etc