ARM64 build on native runner

[jpm-canonical]

Summary

Change workflow job for arm64 build to run on native arm64 runner, rather than emulated on amd64.

Testing Steps

Check if the CI job passes.

[jpm-canonical]

Running on arm speeds it up enough that we could run the tests on arm too. Should we do that?

If we run the tests on both arm and amd, we can split this into two workflows. Will that be more or less maintainable?

[jpm-canonical]

Using separate workflows for AMD64 and ARM64. After removing the git-lfs requirement from the workflow both run successfully.

It looks like promotion of the snap fails on AMD64 when ARM64 does not have a revision in the source branch. Need to investigate this. Does a promote command promote all architectures?

Maybe better to use snap release: canonical/matter-pi-gpio-commander#84 (comment)

[farshidtz]

Splitting this into two workflows results in a lot of replication. This should ideally be one workflow with a job matrix.

Yes, snapcraft promote promotes all builds from one channel to another. I don't think one can specify just one architecture. If using a job matrix for the build and tests, the promotion can happen in a separate job once the previous jobs finish and converge.