chore: update workflows

[sdh100shaun]

WARNING~ PR DESCRIOTION WRITTEN BY COPILOT

Description

This pull request updates various GitHub Actions workflow templates and security workflows to use newer, stable, and more specific action versions. The main changes focus on improving reliability and security by referencing fixed action versions instead of floating or outdated ones, and by upgrading reusable workflow versions across multiple templates.

Workflow action version upgrades:

• Updated all uses of actions/checkout and actions/setup-node to explicit version v6.0.0 instead of v4 in workflow-templates/check-pr-title.yaml, workflow-templates/ci.yaml, and workflow-templates/snyk-monitor.yaml. [1] [2] [3]
• Changed Snyk actions from @master to the stable @v1.0.0 release in Node.js and PHP security workflows (.github/workflows/nodejs-security.yaml, .github/workflows/php-security.yml, .github/workflows/php-library-security.yml, and workflow-templates/snyk-monitor.yaml). [1] [2] [3] [4]

Reusable workflow version upgrades:

• Updated all reusable workflow references (such as nodejs-lint.yaml, nodejs-test.yaml, nodejs-build.yaml, upload-to-s3.yaml, update-lambda-function.yaml, nodejs-publish.yaml, php-library-security.yml, php-library-static.yml, php-library-tests.yml, php-security.yml, php-static.yml, php-tests.yml, terraform-static-full.yaml, and terraform-static.yaml) to use the latest v5.10.0 version (or equivalent) instead of older versions like v4.1.1 or v5.0.6. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]

Security and code scanning improvements:

• Upgraded octokit/graphql-action from v2.x to v3.0.0 and github/codeql-action/upload-sarif from v2 to v3 in PHP security workflows for improved compatibility and features. [1] [2] [3] [4]

These updates help ensure that workflows are more secure, predictable, and benefit from the latest features and fixes.

Related issue: n/a

Before submitting (or marking as "ready for review")

• Does the pull request title follow the conventional commit specification?
• Have you performed a self-review of the code
• Have you have added tests that prove the fix or feature is effective and working
• Did you make sure to update any documentation relating to this change?