Web Client Submit Transaction Fix

[dagarcia7]

Summary

This PR consolidates the submit_transaction and submit_transaction_with_prover calls exposed via WASM in the web client to just submit_transaction.

I made this change because in #720, I tried making it so that the top-level WebClient wrapper that I introduced to allow the web workers work only exposed one submit_transaction call with an optional prover. Then, depending on whether a prover was passed, it would call into submit_transaction or submit_transaction_with_prover as both of these calls were exposed from the rust side. The result of this could be confusing for consumers of the SDK because despite trying to consolidate the calls at the top level, the Typescript typings would still indicate that submit_transaction_with_prover is callable directly.

As a result, I decided to consolidate the calls at the rust level, and fix the JS accordingly. Now there should be no confusion when calling submit_transaction as the it's the only call to make and the parameters are very clear.

[SantiagoPittella]

Overall looks good, left a small comment

[SantiagoPittella]

This should be placed in a new section named ## 0.7.2 (TBD) or similar.

[dagarcia7]

Ah, ok so 0.7.1 hasn't actually been patch released yet, but when I added the section in this PR, I mistakenly put a date for the 0.7.1 section because I didn't know that (TBD) was right way to do it 😅 It's also slightly confusing that I got a bit ahead of myself and published 0.7.1 of the SDK version so now I'm a version ahead in the SDK. In the future, I plan to add some automation around publishing the SDK to fall in line with when releases, patch releases, and merges to the next branch are made so that this desync doesn't happen.

Anyway, all that to say that I think the correct thing here is to keep the 0.7.1 section with a (TBD) and then put this line under this section as well 👍