Prototype build artifact

[namoscato]

This doesn't buy us much but also doesn't hurt in my opinion. I mostly wanted to prototype artifact functionality mentioned in #96 (comment). If we like this approach, we might consider uploading an artifact when linting fails to minimize some of the verbose stdout.

Specifically, this:

• Separates GitHub Action npm commands into separate steps
• Sets GAPI_MAX_PARALLEL: 3 in build / generate job
• Uploads generated types as an artifact in build / generate before deploying*

*I tested this on a forked repository; here's what it looks like:

[Maxim-Mazurok]

My problem with leaving JSON in the types is that we don't want to publish this JSON to the DT. So, I would argue for leaving .tmp directory. Then, we can upload both .tmp and types to build artifacts, and publish only types directory.

[Maxim-Mazurok]

Whould be great to have it finalized, because because my approach of console.logging turned out to be failing for large files. console.log has a limit, so I will have to switch to manually writing to stdout. Instead of applying this fix, I would prefer merging this PR :)

[namoscato]

Sorry, I'll try to circle back to this later today or tomorrow!

[namoscato]

@Maxim-Mazurok, I think I came up with a solid solution that hopefully works for you as well!

This still uploads the full types artifact on success, but to address your lint failure scenario, I ended up leveraging a workflow command to upload the specific types associated with the service that failed.

[namoscato]

Learning more about expression syntax, there is probably an option to minimize some of this duplication, consolidating workflows in favor of conditional logic, but this is duplicated for now.

[Maxim-Mazurok]

Very nicely done 👍 Liked the `::set-env`` approach, thank you!

And yes, it would be nice to figure out how to eliminate duplication from the workflows in the future, create a new issue for this, please.