bump ctf-build-image for platform option

[augustbleeds]

This enables building and testing Chainlink images for both ARM64 and AMD64 architectures. The chainlink stage/prod environments now use arm64 nodes only , but CI tests still depend on AMD64 images so we have to build both. The PR was pointing to some feature branches but now that that the changes have been merged to the main branch of the .github actions repository we can merge these changes in.

I cleaned up the action also to tag the starknet image with the PR commit hash instead of the merged git hash which is confusing since it does not exist and cannot be fetched outside of the initial PR trigger.

After these changes are merged, we'll need to rebase Dimitris's starknet changes and attempt the rollout again.

Here is evidence the build works in staging without a failed ArgoCD rollout: https://github.com/smartcontractkit/infra-k8s/pull/32462

Co-pilot's summary of changes:

Multi-platform Docker builds:

• Changed from single build_chainlink_image job to build_chainlink_images with matrix strategy
• Added support for both linux/arm64 and linux/amd64 platforms
• Uses different runners: ubuntu-24.04-arm for ARM64, ubuntu-24.04 for AMD64

New multi-platform manifest job:

• Added build_multiplatform_image job that combines ARM64 and AMD64 images into a single manifest
• Uses build-push-docker-manifest action to create unified image

SHA handling improvements:

• Added SN_SHA environment variable that properly uses PR head SHA instead of merge commit
• Updated all image tags to use SN_SHA instead of github.sha

Build action upgrade:

• Updated from older [email protected] to @v1.3.0
• Changed from legacy parameters to new platform, dockerfile, plugin-manifest-overrides format

Job dependencies updated:

• run_tests now depends on build_multiplatform_image instead of build_chainlink_image

[github-actions]

👋 augustbleeds, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[augustbleeds]

these were just unused