refactor: Adapt to Sphinx (Refactor proof handling)

[huitseeker]

Summary

This is the companion PR of https://github.com/argumentcomputer/sphinx/pull/150

In Detail

• Update Sphinx dependencies from tag v1.0.0 to branch forward_ports_43 across all components.
• Modification of all instances of SphinxProof in favor of SphinxProofWithPublicValues.
• Inclusion of the run() method call chained after the prove and execute functions across system (enacting builder pattern).
• Removal and integration of separate prove_plonk and verify_plonk functions into main proving and verification functions using the method .plonk() where required.
• Direct passing of stdin as an argument in the execute function across applications.
• Update of the Rust Toolchain from "nightly-2024-07-30" to "nightly-2024-08-13" in both Aptos and Ethereum components.
• Addition of bytes function for supporting different proof types in the fixture-generator.
• Updating proof creation and validation in the fixture generation process with revised function calls.
• Revisions in client and server operations to support SphinxProofWithPublicValues and updated function calls.
• Update of tokio version from "1.39.0" to "1.39.2" and Hex dependency addition at version 0.4.3.

[!IMPORTANT] After https://github.com/argumentcomputer/sphinx/pull/150

[!NOTE] This is a companion PR, what you want to look at the CI result of the penultimate commit. The last commit's failure is expected.

[huitseeker]

Except I'm not 100% sure that the bytes() method in the fixture-generator is correct with the pr.raw_proof/pr.encoded_proof thing

True, I can revert to the encoded proof if this is needed, it's an easy fix.

[wwared]

@samuelburnham: We will need to update the cycle-count-regression CI check due to output format changes, see #164. It's failing for aptos in this PR and the ethereum one is currently only passing because this PR has not yet been rebased on top of #163 so it's not running any tests. This is a lower priority/non-blocking issue that we can solve later on and merge with the failing CI checks if we need to

[storojs72]

I have updated Move tests, so now only cycle-count-regression stuff is broken. As we can tackle this in subsequent PRs, I think this one is good to merge once CI finishes