Enforce npm v7 and node 14+ (#127)

## All renovate PRs will use npm v7

Up until now, renovate was using npm v6 to generate PRs for dependency updates. Because the lockfile format changed from v6 to v7, there was a very big diff in the what deps we're installing. Enforcing npm v7 in package.json makes renovate use npm v7 as well.

## Added npm v7 and node 14+ restrictions to package.json

This should print out a warning if the user is not using those versions of node and npm.

## CI is upgraded to node 16

The `node:14` image bundles npm v6, and is the current LTS, but `node:16` will be LTS soon (October 2021) and bundles in npm v7. So we might as well move our CI to node 16. Right now, CI is installing deps with npm v6, and things can potentially go wrong with that.

## Enabled the dependency dashboard for renovatebot

This should create an issue that acts as a dashboard for tracking all renovatebot PRs.

Reviewed-on: www/www-new#127
Co-authored-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
Co-committed-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>

.drone.yml

@@ -1,30 +1,30 @@
 ---
 kind: pipeline
 type: docker
-name: node14
+name: node16
 
 steps:
 - name: install-deps
-  image: node:14
+  image: node:16
   commands:
   - npm install
 
 - name: lint
-  image: node:14
+  image: node:16
   depends_on:
   - install-deps
   commands:
   - npm run lint
 
 - name: build
-  image: node:14
+  image: node:16
   depends_on:
   - install-deps
   commands:
   - npm run build
 
 - name: export
-  image: node:14
+  image: node:16
   depends_on:
   - build
   commands:

package.json

@@ -1,6 +1,10 @@
 {
   "version": "0.1.0",
   "private": true,
+  "engines": {
+    "node": ">14",
+    "npm": "^7"
+  },
   "scripts": {
     "dev": "next dev",
     "build": "next build",

renovate.json

@@ -1,3 +1,4 @@
 {
-  "$schema": "https://docs.renovatebot.com/renovate-schema.json"
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "dependencyDashboard": true
 }