added tests around minified runtime versions of semver functions

[mpeyper]

In #11271 I wrote some tests to help try an work out what was happening with the runtime versions of the semver functions. I offered to add them to the test suite in that PR and @sokra suggested as a seperate PR to not hold up the bug fix getting through.

There's some pretty nasty code in here to generate the functions with a dummy RuntimeTemplate and evaluate the functions to be runnable in the test suite, so I'm happy to take suggestions on how to make those parts less nasty. I did investigate using new Function(...) instead of eval, but there was an issue with accessing other functions in the module's scope when executing it in a NodeJS environment (some details in the MSDN docs).

What kind of change does this PR introduce?

Tests only.

Did you add tests for your changes?

I only added tests.

Does this PR introduce a breaking change?

No.

What needs to be documented once your changes are merged?

Nothing.

[webpack-bot]

For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

[webpack-bot]

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

[webpack-bot]

@mpeyper Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@sokra Please review the new changes.

[sokra]

Thanks