chore: update gh actions to the latest versions

[davidgamez]

Summary:

This pull request updates the versions of several GitHub Actions used across workflow files to their latest major versions. The updates enhance security, compatibility, and support for newer features in CI/CD pipelines. Additionally, some configuration changes were made to accommodate breaking changes in action inputs.

Key changes include:

GitHub Actions Version Upgrades

• Updated core actions such as actions/checkout, actions/setup-python, actions/setup-java, actions/cache, and actions/download-artifact to their latest major versions (mostly v7 or v8) in all workflow files, improving reliability and support for newer GitHub Actions features. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]

• Upgraded Google Cloud and Docker actions (google-github-actions/auth, google-github-actions/setup-gcloud, docker/login-action) to their latest major versions for improved security and compatibility. [1] [2] [3] [4] [5]

• Updated HashiCorp Terraform setup action to v4 for improved Terraform integration. [1] [2]

1Password and Slack Integration Updates

• Upgraded 1password/load-secrets-action to v4 in all relevant workflows and actions, ensuring compatibility with the latest 1Password API and features. [1] [2] [3] [4] [5]

• Upgraded slackapi/slack-github-action to v4 and updated configuration to use new input-based webhook configuration instead of deprecated environment variables.

Workflow Maintenance and Consistency

• Ensured all artifact upload/download steps use the latest actions/upload-artifact and actions/download-artifact versions for consistency and improved performance. [1] [2] [3] [4] [5] [6]

• Updated Node.js setup action to v7 in assign_next_release_milestone.yml.

These changes ensure that CI/CD workflows remain secure, up-to-date, and compatible with the latest features and best practices on GitHub Actions.

Expected behavior:

Github actions are updated to the latest versions

Testing tips:

Provide tips, procedures and sample files on how to test the feature.
Testers are invited to follow the tips AND to try anything they deem relevant outside the bounds of the testing tips.

Please make sure these boxes are checked before submitting your pull request - thanks!

• Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
• Add or update any needed documentation to the repo
• Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• Linked all relevant issues
• Include screenshot(s) showing how this pull request works and fixes the issue(s)