Use Multi-Arch Build instead of creating separate images

Currently, there exists both community (amd64) and community-aarch64 (arm64) packages.

This is undesirable for multiple reasons:

• It makes it difficult for developers to find the correct images (not helped by Docker Hub's searching)
• It complicates the set-up when using docker compose (and presumably swarm, k8s, etc.), because now two separate docker-compose.ymls need to be created, one specifying community and the other community-aarch64
• It complicates documentation because different example commands need to be used for different architectures.

The preferred method for supporting multiple architectures is to create a single "multi-architecture" image, as outlined here https://docs.docker.com/desktop/multi-arch/
Doing so will allow referencing the single tag community, and the appropriate image for the current architecture will be fetched automatically

I acknowledge that a multi-arch image might not be so simple to build. In any case, thank you for your consideration.

Start with the linked Docker multi-architecture documentation, then inspect how the separate community and community-aarch64 images are built and referenced by docker-compose.yml. Done means the community tag automatically serves the appropriate architecture without separate image names or architecture-specific compose examples.