feat: linux/arm64 support for sync helper

[altitudems]

Is your feature request related to a problem?
The devspacehelper executable assumes amd64 architecture, therefore it will not run inside arm64 containers.

When running devspace dev you end up with an endless loop of 'exec format' errors, as it keeps trying to execute the incompatible binary:

[0:sync:app] Start syncing                   
[0:sync:app] Sync started on /Users/username/Code/app <-> . (Pod: app-66cd4cf65d-cb2b2)
[0:sync:app] Error: Sync Error on /Users/username/app: Sync - connection lost to pod app-66cd4cf65d-cb2b2:  Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "8c56ce6de40ba50aa4e6c26470814d8b7ade37b3d578818217de7e5732448fd3": OCI runtime exec failed: exec failed: container_linux.go:370: starting container process caused: exec format error: unknown
[0:sync:app] Sync stopped
[0:sync:app] Restarting sync...

Which solution do you suggest?

1. Cross compile multiple devspacehelper binaries, including the arch in the filename (e.g. devspacehelper-arm64)
2. Copy the platform appropriate binary to the container
3. Sync to your hearts content on Arm64 instances (AWS EC2, Raspberry Pi clusters, etc.)
4. Proffit ;)

Which alternative solutions exist?
Don't use sync in arm64?

Additional context
Where the the amd64 arch is specified in the build script:
https://github.com/loft-sh/devspace/blob/c4502eb234b5ed322d7474ea2ba061a96b8366d1/hack/build-all.bash#L60

Where the download url is defined before copying the binary to the container:
https://github.com/loft-sh/devspace/blob/d092290ba00d270edf4316dc45add7c613fee009/pkg/devspace/services/sync.go#L42

/kind feature

[altitudems]

This may make things the cross-compile part easier:
https://github.com/mitchellh/gox

[FabianKramm]

@altitudems thanks for creating this issue! Yes I guess we can add arm64 support for the sync helper binary that can be enabled via the sync options.

[FabianKramm]

@altitudems we just released version v5.11.0-beta.0 which you can use via devspace upgrade --version v5.11.0-beta.0, which adds a new config option that installs the arm64 devspacehelper into the container:

dev:
  sync:
  - ...
    arch: arm64

Would be great if you could verify that this fixes the issue

[altitudems]

Just saw this! I'll check it out and let you know :)

[markszente]

I can confirm the arch option solves the issue.

[FabianKramm]

@markszente great then I'll close this issue