Lint for whitespace in tool XML

[neoformit]

Address issue #12207

Whitespace is quite easily introduced into the tool XML version and name properties through the use of tokens:

<!-- This results in version=" 0.0.1 " -->
<token name="@TOOL_VERSION@"> 0.0.1 </token>

@bernt-matthias suggested it would be better to lint for hazardous whitespace rather than parse it out since there are cases where whitespace may be required in tokens. This PR adds some extra linting to warn users of whitespace in <tool> and <requirement> name/version which might cause errors. An additional test was added to test_tool_xml.py to cover this linting.

How to test the changes?

• I've included appropriate automated tests.
• This is a refactoring of components with existing test coverage.

License

• I agree to license these contributions under Galaxy's current license.
• I agree to allow the Galaxy committers to license these and all my past contributions to the core galaxy codebase under the MIT license.

[bernt-matthias]

@neoformit thanks. looks great. can you fix the linter error:

 ./test/unit/tool_util/test_tool_linters.py:4:1: I101 Imported names are in the wrong order. Should be general, inputs

[neoformit]

@bernt-matthias Done :)

[bernt-matthias]

Fine from my side. Thanks a lot.

[jmchilton]

Awesome - thanks so much!

[github-actions]

This PR was merged without a "kind/" label, please correct.