update-actions

Update GitHub Actions

• Find all workflow files in the .github/workflows and .github/actions directories of this repo.
• Use gh to fetch the very latest version of every action referenced in every GitHub Actions workflow file in this repo.
• Update all the action references to their latest version. All actions must be pinned to a full length sha hash.
• Update all uses: docker references within workflow files to their very latest version. All references must use the full length sha256 hash.
• Update all run: uvx references within workflow files to their very latest version. Use exact tag names.
• Ensure every sha reference includes a trailing comment containing the exact tag name which may or may not include a leading v, eg. # 1.2.3 or # v4.0.0. Floating references such as v4 are not allowed.
• Don't update any actions that use a branch reference such as trunk, develop, main, but do flag them in your output.
• If an action or package receives a major version bump, investigate the changelog and update the workflow file to accommodate any breaking changes.
• If the johnbillion/plugin-infrastructure action gets updated, update the same in composer.json and package.json, then run npm install to update package-lock.json.