Node 20 & dependencies upgrade

[lhtdesignde]

Hi,

the import-map-deployer has a critical vulnerability (openssl:3.0.8-r3/CVE-2023-5363) by using an old node version (14).

So I upgraded to the latest LTS Node Version (20) and did some minor package updates, which also fix some vulnerabilities.
The most vulnerabilities are in jest though. At least 13 critical ones but upgrading that breaks the tests, so I left it for now.

Also the package request is deprecated and needs replacing.

• Upgraded to Node LTS 20.17.0
• Package updates
• workflow packages updates
• husky fixes (didn't run pre-commit for me)

The PR addresses also following issues:
#157
#164

[MilanKovacic]

Looks good. Thank you for the contribution.

[joeldenning]

Thanks for your contribution. This caused a regression bug for Azure Storage users in #167 that was fixed in #168

[lhtdesignde]

@joeldenning Thanks for fixing that. I looked into upgrading Azure Storage package as well but as soon as I did that, all tests were failing locally. So I didn't. It was a fairly big update with node 20 and I tried to make sure to look into all packages. Azure Storage didn't mention that the current version would not work with node 20 and all tests passed with the version used here. Just to give you my thought process.
Happy to help if there is another need in the future.

[joeldenning]

It was an easy thing to miss - testing all the io-methods manually is arduous. The tests failed for me, too, after upgrading @azure/storage-blob, but since the tests don't actually execute azure storage code (just import it), I was able to work around it via jest's moduleNameMapper mocking to an empty module