update yeoman-test to v9.

[mshima]

Added a mocha cleanup hook that cleanup yeoman-test context on after.
Mocha seems to somehow reuse a fork pwd when creating a new fork.

• switch to composed generators apis from yeoman-test@v9
• drop a few more manual cleanup.

Fixes #27019.

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[mshima]

Failure is caused by api request, but there is no sample in linked issue.

[emilpaw]

@mshima Was a specific change in this PR responsible for the fix of #27019 or was it just fixed as a side effect to the update?

[mshima]

@emilpaw mocha cleanup hooks that I’ve added to yeoman-test:
https://github.com/yeoman/yeoman-test/blob/main/src/mocha-cleanup.hooks.js

after hook runs once per file(thread) in parallel.

yeoman-test cleanups current environment before a new context is created (a new test is run) or on some exit signals.
In the specific case pwd is not been reverted to the original folder, probably due some mocha thread management logic.

• I don’t know if theads are reused or a new is created.
• It’s not easy to reproduce with a reduced test samples.

In the end manually forcing a yeoman-test cleanup fixes the issue.

[emilpaw]

Thanks for the info @mshima.

I also was not able to find a minimal reproducible example, even after writing a script to automate searching for one. It seemed to require most of the tests and for sure cli-spec was involved.