Bump node from 10.20.1-alpine to 14.4.0-alpine in /server

[dependabot]

Bumps node from 10.20.1-alpine to 14.4.0-alpine.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[patcon]

We should find the newest node version that will build all containers. This makes caching simpler.

node image	status	status *
14 (14.4.0)	❌	✅
13 (13.14.0)	--	✅
12 (12.18.0)	❌	✅
12.5.0	❌	--
12.0.0	❌	--
11 (11.15.0)	✅	✅
10.20.1	✅	✅

*^{With this bcrypt package upgrade patch from 3.0.0 to 3.0.8: https://gist.github.com/patcon/4461f73d2814e7d03a50076a9c6bd0dd}

Error

Long build failure that looks like this: brianc/node-libpq#62

Node version is different, but common factor is node-gyp@3.8.0, which is very far behind current v7.0.0 of today.

EDIT: Seems this is the solution:
brianc/node-pg-native#71 (comment)

I was able to get this working for Heroku and Node v12.13.1 by adding libpq v1.8.9 to my package.json (to allow for the latest fix)

Makes sense, since a fix was released (untagged), as seen in commit log:
https://github.com/brianc/node-libpq/commits/master

EDIT2: ok, seems it's just bcrypt that holds us back. Fixed in patch above.

[patcon]

Seems that we might be ablet to upgrade server to running on the newest node 14, if we'd like.

Any reason not to -- other package incompatibilities that @pol-is/core is aware of? We could just apply the linked patch above to this issue, and see whether our e2e tests pass...?

[patcon]

TODO: apply the patch linked above, and merge to latest 14.x once passing.

patch: https://gist.github.com/patcon/4461f73d2814e7d03a50076a9c6bd0dd

[metasoarous]

LGTM