Draft: Update Github Actions

[ghost]

Fixes #189.

Updated all occurrences of actions/checkout to use the v2 version.

Changed the release job to use softprops/action-gh-release@v1, as used in https://github.com/wasmCloud/wasmcloud-otp.
Wasmcloud-otp creates tarballs for each platform and puts them in the Github Release though, and I wasn't sure if that was something that should be done here. I'm leaning towards no because wash is already distributed through the various package managers, but interested to hear any feedback on that.

[ghost]

Ah didn't see #190 before opening this. That one doesn't appear to update the checkout actions though.

[autodidaddict]

@brooksmtownsend @jordan-rash we should rationalize between this Pr and #190 .

[jordan-rash]

Agree. I think, at this point, I will close #190 and we move forward with this one. The primary focus on #190 was to get brew automation working and not the critical updates that @mattwilkinsonn did here.

Also, in my getting more familiar with brew, it turns out, deep in the bowels of their documentation, there is a better way than what I proposed in #190. So I will leave the branch there, but we can get rid of the PR for now.

[jordan-rash]

One thing that sticks out here is the linting. We should probably have a common action that does a linting check on the yaml for all our GHAs.

[ghost]

One thing that sticks out here is the linting. We should probably have a common action that does a linting check on the yaml for all our GHAs.

Yeah I noticed that as well. The YAML formatter I have on VSCode auto fixed it, but could be useful to have it lint in the CI itself.

Some google searching led me here https://github.com/marketplace/actions/yaml-schema-validator and https://github.com/marketplace/actions/yaml-lint

[brooksmtownsend]

This looks great! I agree with you that there's no need to compile+attach the wash binary since we already have other mechanisms for distribution. As long as the actions pass this LGTM