build(dependencies): prefer Yarn and avoid loose versions

[angrybacon]

• Add Quick Start instructions in CONTRIBUTING.md

• Prefer yarn over npm

  npm is slower, npm leads more easily to dependency hell(s) which usually require manual resolving. Here are the 2 commands you'll need (mostly)

  • yarn install or simply yarn: same as npm install
  • yarn add foobar: add foobar dependency. Add -D to add as dev dependency

  The rest is mostly the same, except you don't have to type run to run your scripts like you would with npm. yarn start and not yarn run start

  Once you've installed Yarn, you probably want to nuke your node_modules folder before running yarn install

• Prefer exact versions for all dependencies

  -"some-package": "^3.1.2"
  +"some-package": "3.1.2"

  Loose versions lead to setups and bugs harder to reproduce. Added .yarnrc configuration file so that the behavior is automatic whenever you add more dependencies

• Ensure Node v16

  Apparently the project could not run with Node v18 (my usual default) so the setup should now complain when the current Node version does not match what is set in package.json

  Type node -v to check your current version

  The recommended way of working with that is to use nvm (see .nvmrc). Let me know if you need help setting that up on your machine