Update GitHub actions using deprecated runtimes

[aaemnnosttv]

Feature Description

Some GitHub actions that we use have started to raise deprecation warnings.

E.g.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3, actions/setup-node@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

This is not an exhaustive list, but an example that references several actions that we use across many workflows.

See also #6188

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• All GitHub action workflows should be audited for workflows using deprecated runtimes (this is surfaced in workflow runs as an annotation (example))
• All actions using deprecated runtimes should be upgraded to a version that is free of deprecations
  • In the absence of an upgrade that satisfies this criteria, steps should be outlined for each instance to be upgraded or replaced in the future and the relevant deadline that this must happen by

Note: this has no effect on the Node runtime used in our jobs (i.e. controlled by nvmrc) it's specific to the runtime used by actions

Implementation Brief

• Update all usage of actions/checkout@v3/actions/checkout to actions/checkout@v4
• Update all usage of actions/setup-node@v3/actions/setup-node to actions/setup-node@v4
• Update google-github-actions/auth@v1 to use google-github-actions/auth@v2. From the changelog for google-github-actions/auth it does not look like there are any obvious breaking changes that would prevent us from upgrading.
• Update peter-evans/find-comment@v2 to v3
• Update peter-evans/create-or-update-comment@v2 to v4

Note: the compressed size action (see: https://github.com/google/site-kit-wp/actions/runs/8467166896) uses Node 12 and has no upgrade path, so it won't be updated.

Test Coverage

• No test updates needed, but check all actions to ensure no deprecation notices appear for Node 16 usage from our actions.

QA Brief

• No QA needed; CI tests passing is all that's needed. Once merged, this can be moved directly to approval. 🙂

Changelog entry

• N/A

[eugene-manuilov]

IB ✔️

[eugene-manuilov]

Moved straight to Approval since there is nothing to QA.

[aaemnnosttv]

❌ Approval

There are still a number of instances of actions that need updating as can be seen in the annotations of action runs such as this one https://github.com/google/site-kit-wp/actions/runs/9513898534

Please open a follow up issue to address the remaining instances.