chore: Avoid Rosetta on Apple

[apljungquist]

This speeds up both building and using the dev container by a lot on Apple silicon, see benchmarks below. Unfortunately, the checksums do not reproduce and developers would have to either wait for PRs to fail once in CI or run the image with --platform linux/amd64.

The major workflows check_other, check_generated_files, check_generated_files_container all work in the new dev container on an aarch64 host. What doesn't work is running some apps on in the container (as opposed to on device). These can run outside the container in most cases so in the unlikely event that it impacts anyone, there's a workaround available.

Benchmarks

These ran on an Apple M4 Max.

time docker build --no-cache -f .devcontainer/Dockerfile .:

• before: 5:55.01
• after: 3:08.48 (-47%)

These are the steps that took the most time:

                                                          Before  After
 => [stage-2  9/10] RUN ./install-system-packages.sh ...   58.6s  22.0s
 => [stage-2 10/10] RUN --mount=type=bind,target=/con ... 245.7s 119.4s
 => exporting to image ...                                 45.4s  44.3s
 => => exporting layers ...                                30.8s  30.6s
 => => unpacking to ...                                    14.6s  13.7s

Unsurprisingly, the most time saved was from commands running containerized. These run more than twice as fast. This is reflected also when building apps inside the dev container:

rm -r target-aarch64/
time make build

• before: 0m20.285s
• after: 0m7.264s (-64%)

Details

.devcontainer/Dockerfile:

• Update to Debian trixie to avoid version 'GLIBC_2.39' not found errors when running cargo-acap-sdk. The best explanation I could find for this is that the host pre-built standard lib depends on different versions depending on the platform they were build on.

.devhost/install-rust.sh:

• Use platform appropriate rustup-init to avoid the problem documented in Add explicit platform to Dockerfile FROM statements #70.

README.md:

• Update the suggested docker commands to one that can easily be adapted to run make check_generated_files_container. Note that inspect_env still doesn't reproduce.

Footers

Related-to: #229

[apljungquist]

Moving this back to draft because the #[cfg(not(any(target_arch = "x86_64", target_os = "macos")))] may not work in the new container because 😐

And cargo-acap-sdk fails to start: cargo-acap-sdk: /lib/aarch64-linux-gnu/libc.so.6: version 'GLIBC_2.39' not found (required by cargo-acap-sdk)