feat: Add support for jobs.

[scstorytel]

Revisiting #422 to add support for jobs.
These are the same set of changes.

Tests all pass for node 16, ran using npm test.

[scstorytel]

Hello @sethvargo,

Do you need me to rebuild/retest this for Node 20?

[nick-youngblut]

Any updates on this? It would be great to have support for Cloud Run jobs.

[banderson623]

This would be pretty great to add 👍

[braveenth]

+1 Added support for Jobs yaml here: https://github.com/braveenth/deploy-cloudrun/tree/add-cloud-run-job-yaml-support

[atrauzzi]

@sethvargo @averikitsch -- Is there any chance this or #422 can be moved forward? Would really like to be able to get up and running with it! 🙂

[iennae]

@scstorytel could you resolve the currently conflicting files? I can take a look after that. Thanks.

[scstorytel]

@iennae I've updated the jobs tests and built the new version. Have a look and lmk if it all looks good please.

[scstorytel]

@iennae Updated everything again. This might be my inexperience with javascript speaking, but maybe we should not track things like package-lock.json, since that's just a generated file that tells you what you have installed? Same with index.js, since that's just the build output. It seems to create unnecessary/redundant conflicts.

[TigerC10]

@scstorytel we do want to track package-lock.json because it pins the versions of 3rd party dependencies installed. The package.json can specify version numbers in the form ^6.0.0 which would indicate "anything compatible with 6.0.0" rather than the specific 6.0.0 versioned release. The package-lock will specify which exact version was installed.