add jasmine-node command-line program (fixes #31461)

As noted in #31461, this formula does the following in order to get a working node CLI program bootstrapped:

- Vendor production dependencies (`npm install --production)
- Depends on `brew` provided `node` and `npm`

I thought about vendoring `node` itself; however, downloading the binary `node` just seemed wrong.

One caveat is that if you've also installed node via `nvm` (like I have), then this installed program will use whatever version of node it has active. I feel like this is a fair trade-off for keeping the formula simple. We could do a replace on the shebang and pin `node` to the one in the Cellar; however, this seems like overkill.


> To elaborate `--version` is better than nothing but it'd still be good to have a decent test in here.

The only thing I can think of that would be any better would be to perhaps build a simple test file. Perhaps we could heredoc a test into the temp directory and execute it. It should be a test that will always pass (`expect(1, 1)`) so the exit status is `0`.

Are there any examples of formula that does such a thing that you can think of or is this a first?