Call the mega-linter-runner installer to generate the examples in the docs

[echoix]

Currently only in draft state, but it minimally is able to call the yeoman generator as a npm test. It can be saved to a file, so it can then be replaced in the docs.

Ideally, it would help out #3032

I want feedback on:

• Where to save files
• Should we remove the folder before and after inside the ./build.sh, or should we commit them as generated files
• What options chosen in the generator would we like to show in the docs
• Correct usage of modern node.js and mocha things. I don't know a lot about node.js, and I fought a lot for the yeoman test helper to be able to find the script and the template, so it may not seem right as it is now.
• Should we generate for all the other CI providers (I think so)
• The name of the script

Proposed Changes

1. …
2. …
3. …

Readiness Checklist

Author/Contributor

• Add entry to the CHANGELOG listing the change and linking to the corresponding issue (if appropriate)
• If documentation is needed for this change, has that been included in this pull request

Reviewing Maintainer

• Label as breaking if this is a large fundamental change
• Label as either automation, bug, documentation, enhancement, infrastructure, or performance

[echoix]

See the example in the README of https://github.com/yeoman/yeoman-test (I didn't understand everything)

And some other partially outdated examples here https://yeoman.io/authoring/testing

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this pull request should stay open, please remove the O: stale 🤖 label or comment on the pull request.