Add yarn cache to workflow and make sure it's working

[godber]

@jsnoble had added the yarn cache to some of his node setup actions as did I, but I thought they weren't working. I did just find some evidence of this working on the standard-assets project:

• Here it says the cache was found and used:
  • https://github.com/terascope/standard-assets/actions/runs/5193111840/jobs/9363254637
• Caches show up here:
  • https://github.com/terascope/standard-assets/actions/caches

Obviously this is a feature we want, but we want to make sure we understand it well enough to use it properly, we want it to work.

[godber]

Oh, the kafka asset has caches too ...

https://github.com/terascope/kafka-assets/actions/caches

Maybe I just don't understand when the cache gets used. I had assumed, perhaps erroneously, that they were not working because of messages like this on the node setup action

Run actions/setup-node@v3
Found in cache @ /opt/hostedtoolcache/node/14.21.3/x64
Environment details
/usr/local/bin/yarn --version
1.18.0
/usr/local/bin/yarn cache dir
/home/runner/.cache/yarn/v4
yarn cache is not found

ref: https://github.com/terascope/kafka-assets/actions/runs/5147923655/jobs/9268939754

[godber]

Oh, I'm confusing the tool cache with the yarn cache ... this message is about the toolcache, which is where node setup gets it's node release for a specific version

Found in cache @ /opt/hostedtoolcache/node/18.16.0/x64

[godber]

The ES asset uses yarn caching:

https://github.com/terascope/elasticsearch-assets/actions/runs/6152885489/workflow#L26

or here:

https://github.com/terascope/elasticsearch-assets/blob/1125ce461c3e97290a98c0c402bcd46632169861/.github/workflows/test-asset.yml#L26