Update setup-go action for latest version

[katiem0]

Existing actions/setup-go@v3 usage is referring to legacy/deprecated node16 in the actions:

runs:
  using: 'node16'
  main: 'dist/setup/index.js'
  post: 'dist/cache-save/index.js'
  post-if: success()

This PR updates the setup-go action to use latest version.

Confirmed stripped down logic is successful in GitHub CLI extension: katiem0/gh-collaborators

No identified breaking changes are introduced between v3 and v5.

[andyfeller]

Thank you for improving the GitHub CLI and supporting extension authors, @katiem0! 🫶

Does it make sense to bubble up new inputs to allow users to control whether and how caching is used?

☝️ is my only concern as it is not a pure binary off/on as it also involves cache-dependency-path too. 🤔

Accidentally selected approve when I intended to leave a comment

[katiem0]

@andyfeller Can definitely add to it! Wasn't sure if we'd want to add more features - currently the action fails because of the node16 usage, so wanted to get it to a working state asap. Happy to add it in if we want that, but maybe a tech-debt/new issue for it to ensure we're accounting for the new input scenarios? 😄

[andyfeller]

@andyfeller Can definitely add to it! Wasn't sure if we'd want to add more features - currently the action fails because of the node16 usage, so wanted to get it to a working state asap. Happy to add it in if we want that, but maybe a tech-debt/new issue for it to ensure we're accounting for the new input scenarios? 😄

Yeah, I can buy into deferring that until someone has a problem with it and we know more. At the very least, is it worth updating the README to call out that Go dependencies are cached?

[katiem0]

@andyfeller README now has NOTE indicating the change and pointing to the action version from setup-go.