Support Yarn 2, especially regarding stricter peerDependencies constraints

Describe the bug Quasar does not specify Vue as peer dependency but imports from it. I’m using yarn@2 and it much stricter and is not allowing package to use other packages without specifying them as dependencies.

Codepen/jsFiddle/Codesandbox (required) https://github.com/Demivan/quasar-yarn-2-issue

To Reproduce Steps to reproduce the behavior:

1. Checkout repository
2. run yarn build
3. See build error.

Expected behavior No build error should be produced.

Screenshots With webpack

ERROR in ./.yarn/cache/quasar-npm-1.12.13-43fa104864-2.zip/node_modules/quasar/src/utils/open-url.js 1:0-21
Module not found: Error: A package is trying to access another package without the second one being listed as a dependency of the first one

Required package: vue (via "vue/dist/vue.runtime.esm.js")
Required by: quasar@npm:1.12.13 (via ./.yarn/cache/quasar-npm-1.12.13-43fa104864-2.zip/node_modules/quasar/src/utils/)

With rollup:

(node:139528) [MODULE_NOT_FOUND] Error: quasar tried to access vue, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
(Use `node --trace-warnings ...` to show where the warning was created)

Platform (please complete the following information): Yarn: yarn@2 berry

Additional context Fix using .yarnrc.yml: https://github.com/Demivan/quasar-yarn-2-issue/blob/fix/.yarnrc.yml

[yusufkandemir]

@maggie0002 @taai the error regarding resolving Vite’s version (TypeError: Cannot read property 'version' of undefined) will be addressed in #13609.

[rstoenescu]

Please use Yarn v1 for the moment. The v2 of Yarn has some hard requirements that forces us to not be able to provide a good developer experience.

We have plans to create a CLI based on Vite instead of Webpack and that will allow us to officially support Yarn 2.