Upgrade dependencies

[fendor]

Also, decide to use yarn for development instead of npm. The decision is completely arbitrary, but we did have both yarn.lock and package-lock.json, and this decides we only need the former.
Decision subject to debate.

The big change here is that all dependencies are upgraded and deprecated dependencies are removed, most notably request has been replaced by bent.

[hasufell]

npm ERR! The `npm ci` command can only install with an existing package-lock.json or
npm ERR! npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@[5](https://github.com/haskell/vscode-haskell/runs/5807360080?check_suite_focus=true#step:9:5) or
npm ERR! later to generate a package-lock.json file, then try again.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\npm\cache\_logs\2022-04-03T18_2[7](https://github.com/haskell/vscode-haskell/runs/5807360080?check_suite_focus=true#step:9:7)_3[8](https://github.com/haskell/vscode-haskell/runs/5807360080?check_suite_focus=true#step:9:8)_180Z-debug-0.log

[hasufell]

Did you test the extension after the update?

[fendor]

@hasufell Yes, I tested that the hoogle command still works (which uncovered an error) since it is the main feature hit by these changes and that the extension can successfully setup HLS.

However, I did not test the changes to build.yml, not sure how would be the best way.