[pipeline] add multiarch mco

[nammn]

Summary

• adding multiarch to the operator

Proof of Work

• passing ci while skipping arm
• passing ci while running arm build
• pulling multiarch image

docker run --rm -it --platform linux/arm64 --entrypoint sh 268558157000.dkr.ecr.us-east-1.amazonaws.com/dev/mongodb-kubernetes:6852aae56808a40007526b93
Unable to find image '268558157000.dkr.ecr.us-east-1.amazonaws.com/dev/mongodb-kubernetes:6852aae56808a40007526b93' locally
6852aae56808a40007526b93: Pulling from dev/mongodb-kubernetes
88dac9674920: Already exists 
01860f9dcfa8: Pull complete 
ef547372e92b: Pull complete 
e177c021bea7: Pull complete 
f10b6cc419b7: Pull complete 
05a62aa57d3f: Pull complete 
Digest: sha256:5c158225fad4d9b92b28b43e034f46eaacc6488e74846e3e22fc6e5d0b243e05
Status: Downloaded newer image for 268558157000.dkr.ecr.us-east-1.amazonaws.com/dev/mongodb-kubernetes:6852aae56808a40007526b93
sh-5.1$ uname -a
Linux 0c05ec3b5548 6.10.14-linuxkit #1 SMP Tue Apr 15 16:00:54 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
sh-5.1$ 

(venv) ~/projects/mongodb-kubernetes git:[multi-arch-mco]
docker run --rm -it --platform linux/amd64 --entrypoint sh 268558157000.dkr.ecr.us-east-1.amazonaws.com/dev/mongodb-kubernetes:6852aae56808a40007526b93
Unable to find image '268558157000.dkr.ecr.us-east-1.amazonaws.com/dev/mongodb-kubernetes:6852aae56808a40007526b93' locally
6852aae56808a40007526b93: Pulling from dev/mongodb-kubernetes
ff6f4d5fce2a: Already exists 
8c4dc0e68dba: Pull complete 
433bb9a7e77e: Pull complete 
3f00ac9cf359: Pull complete 
11b2571dd667: Pull complete 
05a62aa57d3f: Pull complete 
Digest: sha256:5c158225fad4d9b92b28b43e034f46eaacc6488e74846e3e22fc6e5d0b243e05
Status: Downloaded newer image for 268558157000.dkr.ecr.us-east-1.amazonaws.com/dev/mongodb-kubernetes:6852aae56808a40007526b93
sh-5.1$ uname -a
Linux 03d6c9cd16d9 6.10.14-linuxkit #1 SMP Tue Apr 15 16:00:54 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you checked for release_note changes?

Reminder (Please remove this when merging)

• Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
• Our Short Guide for PRs: Link
• Remember the following Communication Standards - use comment prefixes for clarity:
  • blocking: Must be addressed before approval.
  • follow-up: Can be addressed in a later PR or ticket.
  • q: Clarifying question.
  • nit: Non-blocking suggestions.
  • note: Side-note, non-actionable. Example: Praise
  • --> no prefix is considered a question

[nammn]

all of those repo changes should be fine as they are targeting $(inputs.params.registry) which points to ecr