feat(proofs): add preferred witness type in circuit's genProof function

[ctrlc03]

Description

Remove isArm check in circuits and instead accept a parameter to decide which witness type to use. Made appropriate changes in tests and cli.

This allows to use wasm witness in an intel chip as well should this be preferred.

Confirmation

• I have read and understand MACI's contributor guidelines and code of conduct requirements.
• I have read and understand MACI's GitHub processes documentation.
• I have read and understand MACI's testing guide.

[netlify]

✅ Deploy Preview for maci-typedoc ready!

Name	Link
🔨 Latest commit	2b95044
🔍 Latest deploy log	https://app.netlify.com/sites/maci-typedoc/deploys/6596db30bd09e700082307fb
😎 Deploy Preview	https://deploy-preview-925--maci-typedoc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[kittybest]

The code lgtm.
I believe the objective of this pull request is to enable wasm support on Intel chips, if users prefer. However, considering that most users might simply want the code to be executable, I propose retaining the isArm() check in genProof. Additionally, we can introduce useWasm as a parameter for those interested in experimenting with options beyond the default configuration.
If I misunderstood it, please tell me~~

[ctrlc03]

The code lgtm. I believe the objective of this pull request is to enable wasm support on Intel chips, if users prefer. However, considering that most users might simply want the code to be executable, I propose retaining the isArm() check in genProof. Additionally, we can introduce useWasm as a parameter for those interested in experimenting with options beyond the default configuration. If I misunderstood it, please tell me~~

mm I like this thinking, it would definitely make it easier for users to use. We could make the flag useWasm optional, and then add some more checks, I'll do that now