chore: migrate the monorepo to pnpm

[yusufkandemir]

What kind of change does this PR introduce?

• Other, please describe: migrate the repo to pnpm workspaces from yarn workspaces / npm mix

Does this PR introduce a breaking change?

• No

The PR fulfills these requirements:

• It's submitted to the dev branch (or v[X] branch)

Other information:
Summary of changes:

• migrate to pnpm from yarn/npm mix
• add app-webpack, cli, and create-quasar to workspaces
• update CI workflows
• improve/centralize linting configuration/packages
• reference the active package manager in app-vite/app-webpack banners
• print pnpm and bun versions in quasar info
• improve/fix some package-manager-related types in app-vite/app-webpack
• improve package-manager-related mentions in docs
• improve the contribution guide in the docs, and reference the docs in /CONTRIBUTING.md and .github/CONTRIBUTING.md to avoid duplicate/out-of-sync content
• update VS Code configuration

[github-actions]

UI Tests Results

   74 files  1 701 suites   2m 1s ⏱️
  504 tests   504 ✅ 0 💤 0 ❌
1 566 runs  1 566 ✅ 0 💤 0 ❌

Results for commit 4a4c01c.

♻️ This comment has been updated with latest results.

[github-actions]

Build Results

JSON API

📜 No changes detected.

Types

📜 Changes detected:

diff --git a/./current-build/types/tsconfig.json b/./pr-build/types/tsconfig.json
index 56822e7..8cb4af8 100644
--- a/./current-build/types/tsconfig.json
+++ b/./pr-build/types/tsconfig.json
@@ -4,7 +4,7 @@
     "lib": ["es2015", "dom"],
     "paths": {
       "quasar": [
-        // index.d.ts is auto-generated by the build process ("yarn build js types")
+        // index.d.ts is auto-generated by the build process ("pnpm build js types")
         // It contains auto-generated types like QInput, QInputProps, etc.
         // To reference those types, import them from "quasar"
         // For other types defined in this directory, use relative imports