updated nodejs dependencies, moved local build steps for codegen to docker, general improvements

[jameslinjl]

Noticed a couple of issues within the nodejs code bindings:

• The dependency versions were somewhat dated, so I brought them roughly up to present day supported versions.
• The generated code could vary based one's local environment. In order to reduce possible variation, I moved the build process over to Docker, which will increase consistency and lower the tooling installation hurdles for updates.
• Added a package-lock.json file to further reduce generated code variation due to shifting of indirect dependency versions.
• Clarified in the package.json that the codegen is to be performed with the latest Node.js LTS version (v18.12.1).
• Bumped release version to 0.0.7. If this looks good to folks, would be great for someone with permissions to publish a new version of the library!

[jameslinjl]

@derhuerst thanks for the feedback!! your suggestions make sense to me and i have implemented changes to address :)

[jameslinjl]

small poke @isabelle-dr - would be great to get some 👀 from someone on MobilityData side!

[isabelle-dr]

Thanks for the ping @jameslinjl!

I will go ahead and merge this PR since it looks like all the review comments have been addressed. Many thanks to @derhuerst and @gauthier-th for the reviews 🙏

[jameslinjl]

thanks @isabelle-dr ! when convenient, it would be great for someone with write permissions for the NPM package to publish a new version of the package (should just be following these instructions)

[isabelle-dr]

@fredericsimard, is this something you can do? 😊

[fredericsimard]

@isabelle-dr If you're asking me if I have login credentials on NPM's website, no I do not. I don't even know what this is. I've looked in all vaults, nothing with NPM or node in them.

[gauthier-th]

@bdferris @barbeau I saw you published previous versions of the package on NPM. Could you help us on this please?