Use protobuf aarch64 binaries for ARM processors

[namloan]

aarch64 binaries have been available since version 3.5.0, therefore it shouldn't be needed to default to x86_64.

I could successfully run the app in an Apple M2 Pro. Would be great if someone with M1 could test and verify.

[alvasw]

Hi @namloan!
We need to switch to the Tor (and potentially Electrum) too. Otherwise Bisq 2 cannot connect to other nodes.

[alvasw]

utACK

[alvasw]

@namloan Please sign your commits with your GPG key. For further details see: https://github.com/bisq-network/bisq/blob/master/CONTRIBUTING.md#sign-your-commits-with-gpg

[namloan]

@alvasw sure, will sign the commit.

Based on your comment I was under the impression that it was absolutely needed to also make the swtich in the Tor and Electrum binaries or otherwise this change would break those integrations. Did I misunderstand? I only tested this on clearnet.

[alvasw]

Based on your comment I was under the impression that it was absolutely needed to also make the swtich in the Tor and Electrum binaries or otherwise this change would break those integrations. Did I misunderstand? I only tested this on clearnet.

Your PR only uses the aarch64 Protobuf compiler, so the build should be faster on M1s/M2s. The compiled output is still not aarch64. To support M1s/M2s natively, we need to update the Tor and Electrum binaries, and tell jpackage to create a aarch64 package.