Add Arkworks and Noname integration details to documentation

[mysteryon88]

Pull Request type

• Documentation content changes

What is the current behavior?

The current documentation for Groth16 verifier deployment does not mention Arkworks-based circuits or Noname as supported tooling options.

Issue Number: N/A

What is the new behavior?

This PR enhances the documentation by explicitly describing compatibility with Arkworks and Noname, making it clearer for users coming from these ecosystems that they can integrate their existing tooling.

Specifically, this change:

• Documents how Arkworks-based Groth16 circuits can be integrated using the ark-snarkjs library to export proofs and verifying keys into garaga-compatible JSON format (BN254 and BLS12-381 supported).
• Mentions Noname as an alternative circuit language that can be compiled to SnarkJS-compatible R1CS, similarly to Circom.
• Adds references to relevant open-source tools and articles to help users get started more easily.

Does this introduce a breaking change?

• Yes
• No

Other information

I really enjoyed working with your tool — great job on the design and developer experience 🙌
While experimenting, I noticed that the documentation doesn’t currently mention Arkworks or Noname, even though they are used in the ecosystem.

I recently successfully verified Arkworks-generated Groth16 proofs on Starknet, so it’s safe to say that this workflow works in practice. You can find an example here: zk-starknet-examples

For this integration, I used ark-snarkjs and added a dedicated export function to produce garaga-compatible JSON, specifically to make this flow smoother.

I thought it would be useful for other developers to know that Arkworks and Noname are fully compatible options alongside Garaga, and hopefully this documentation update helps make that clearer.