chore: fix intermittent arm docker build errors

[mkurapov]

Changes proposed in this pull request

• Use arm ubuntu runners when building arm docker images

Context

Sometimes when we would build a docker image for arm architecture, we would get the following error:

#11 [base 6/6] RUN --mount=type=cache,id=pnpm,target=/pnpm/store     pnpm fetch     | grep -v "cross-device link not permitted\|Falling back to copying packages from store"
#11 6.752 Importing packages to virtual store
#11 23.01 qemu: uncaught target signal 4 (Illegal instruction) - core dumped
#11 24.93 Already up to date
#11 24.93 Progress: resolved 1, reused 0, downloaded 0, added 0
#11 24.93 Progress: resolved 2561, reused 0, downloaded 0, added 0
#11 24.93 Progress: resolved 2561, reused 0, downloaded 1, added 0
#11 24.93 Progress: resolved 2561, reused 0, downloaded 16, added 10
#11 24.93 Illegal instruction (core dumped)
#11 DONE 25.6s

This is a result of a mismatch between the target docker build architecture, and the architecture of the machine that it is running on. This fix makes sure we use an arm based machine to build our arm images.

Resource for selecting GitHub hosted runners:

https://docs.github.com/en/actions/reference/runners/github-hosted-runners#standard-github-hosted-runners-for-public-repositories

---

Fix #3730

Checklist

• Related issues linked using fixes #number
• Tests added/updated
• Make sure that all checks pass
• Bruno collection updated (if necessary)
• Documentation issue created with user-docs label (if necessary)
• OpenAPI specs updated (if necessary)

[netlify]

✅ Deploy Preview for brilliant-pasca-3e80ec ready!

Name	Link
🔨 Latest commit	1853959
🔍 Latest deploy log	https://app.netlify.com/projects/brilliant-pasca-3e80ec/deploys/69382d94135ac000088f9428
😎 Deploy Preview	https://deploy-preview-3732--brilliant-pasca-3e80ec.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

🚀 Performance Test Results

Test Configuration:

• VUs: 4
• Duration: 1m0s

Test Metrics:

• Requests/s: 45.87
• Iterations/s: 15.31
• Failed Requests: 0.00% (0 of 2760)

📜 Logs

> performance@1.0.0 run-tests:testenv /home/runner/work/rafiki/rafiki/test/performance
> ./scripts/run-tests.sh -e test "-k" "-q" "--vus" "4" "--duration" "1m"

Cloud Nine GraphQL API is up: http://localhost:3101/graphql
Cloud Nine Wallet Address is up: http://localhost:3100/
Happy Life Bank Address is up: http://localhost:4100/
cloud-nine-wallet-test-backend already set
cloud-nine-wallet-test-auth already set
happy-life-bank-test-backend already set
happy-life-bank-test-auth already set
     data_received..................: 996 kB 17 kB/s
     data_sent......................: 2.1 MB 35 kB/s
     http_req_blocked...............: avg=7.1µs   min=2.25µs   med=5.9µs    max=685.07µs p(90)=7.16µs   p(95)=7.69µs  
     http_req_connecting............: avg=437ns   min=0s       med=0s       max=554.5µs  p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=86.55ms min=7.87ms   med=71.94ms  max=469.28ms p(90)=147.59ms p(95)=170.8ms 
       { expected_response:true }...: avg=86.55ms min=7.87ms   med=71.94ms  max=469.28ms p(90)=147.59ms p(95)=170.8ms 
     http_req_failed................: 0.00%  ✓ 0         ✗ 2760
     http_req_receiving.............: avg=84.15µs min=20.58µs  med=75.07µs  max=2.31ms   p(90)=101.65µs p(95)=116.4µs 
     http_req_sending...............: avg=34.61µs min=11.91µs  med=26.8µs   max=1.38ms   p(90)=37.12µs  p(95)=47.35µs 
     http_req_tls_handshaking.......: avg=0s      min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=86.44ms min=7.7ms    med=71.76ms  max=469.19ms p(90)=147.45ms p(95)=170.69ms
     http_reqs......................: 2760   45.866065/s
     iteration_duration.............: avg=261ms   min=169.03ms med=249.89ms max=960.26ms p(90)=318.86ms p(95)=343.29ms
     iterations.....................: 921    15.305306/s
     vus............................: 4      min=4       max=4 
     vus_max........................: 4      min=4       max=4 

[mkurapov]

Likely not necessary with the runs-on change, but adding just to explicitly state which platform to build for

[mkurapov]

The docker image scans will be resolved separately