fix: fix compatibility with quasar 2.16.x (fix #373)

[antonio-masotti]

What kind of change does this PR introduce? (check at least one)

• [x ] Bugfix
• [ ] New test runner
• [ ] Documentation
• [ ] Feature
• [ ] Code style update
• [ ] Refactor
• [ ] Build-related changes
• [ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

• [x] Yes
• [ ] No

If yes, please describe the impact and migration path for existing applications:

Only compatible with quasar >= 2.16.0, due to changes in the core quasar build modules (esm modules renamed to quasar.client.js. See comment in the issue there

The PR fulfills these requirements:

• [x] It's submitted to the dev branch and not the master branch
• [x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
• [ ] It's been tested on Windows
• [x] It's been tested on Linux
• [x] It's been tested on MacOS
• [] Any necessary documentation has been added or updated in the docs (for faster update click on "Suggest an edit on GitHub" at bottom of page) or explained in the PR's description.

[antonio-masotti]

Fixes #373

[IlCallo]

Thanks for contributing! Luckily Jest allow for cascading mappings, so we can support both the old and the new Quasar versions

See https://jestjs.io/docs/configuration#modulenamemapper-objectstring-string--arraystring

I see you also noticed that we now need to import all used Quasar components, as it is for Vitest I think it used to work anyway in the past because the Quasar build we previously used included all Quasar components instead of properly tree-shake them

I updated the Jest AE templates to reflect this change

I also updated and test the new configuration with app-webpack-v3 too

I'm gonna merge this PR and release a new version soon