Add Node.js to reduce friction deploying Node projects

[kulor]

Without Node installed in this image, you can't build Node projects just using Github Actions.

Creating this PR does beg the question; is there an intended intermediate step to build your code with to remain language compilation agnostic (Hook scripts)?

[tj]

I thought about that, it would be nice to just use Up's hooks, but I'm not sure it's feasible to support every language in one docker image (let alone every version of each). I thinkkk it might be best to leave those to a separate action

[kulor]

Do you have any suggestions of how you'd decouple the up build from the underlying language without adding a lot of moving parts and complexity?

To avoid aforementioned complexity I think breaking out extra steps into language specific actions (apex/actions/up/nodejs, apex/actions/up/python...) would be the way to go. Thoughts?

[tj]

I definitely agree it'd be nice to retain the hooks. Maybe we could leverage these ones https://hub.docker.com/r/lambci/lambci since they have all the versions. I'll try to check that out today!

[kulor]

Yea, simply replacing FROM golang:1.11 to FROM lambci/lambci:latest could be all that's needed and bonus that it's the same Lambda runtime versions.

[Siilwyn]

Would be great if this can be merged for now.

[jorisvdz]

Maybe this could be implemented with some flag/config option? Would be rally helpful!