Allow forc deploy to submit transaction without waiting for commit confirmation

[luisburigo]

Description

The current forc deploy command is designed to submit and await for transaction finalization as much this is a common use case, for delayed transactions, were transaction are submitted but can take time a lot of time to be included and finalized. For this use cases I have implement a suggestion --submit-only this will follow the current flow, but only submit the transaction.

Example use case for delayed transactions

In Bako Safe, as it is a multisig, it is necessary to have signatures from multiple accounts before sending the transaction to the network. To work together with forc deploy, a GraphQL Proxy has been developed that works with the Fuel provider to allow sending the transaction to our protocol.

forc deploy --node-url 'https://api.bako.global/v1/graphql' --default-signer --submit-only

Changes

• Add a new deploy params --submit-only
• Create a branch on the code to verify if the param is provided
• Abstract create artifacts to a single function to avoid code repetition
• Modified transaction submission to allow for immediate submission when the submit_only command is provided
• Implemented tests for the new command

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[CLAassistant]

All committers have signed the CLA.

[sdankel]

Thank you for the PR! The use case makes sense, and the changes look look to me. Just a few nits.

Heads up, there will be som merge conflicts with #6069 and #6278 if they get merged first.

[luisburigo]

Hey @sdankel , is it necessary to include --submit-only in the forc deploy documentation? If so, which file should I add it to?

[sdankel]

Hey @sdankel , is it necessary to include --submit-only in the forc deploy documentation? If so, which file should I add it to?

Hey @luisburigo - good call out, and yes we should include it in the docs here. It would be great if you could add a short section at the end about multisig with --submit-only.

[sdankel]

Small nit about the documentation - otherwise LGTM :)

[K1-R1]

lgtm, but CI is failing on spellchecking the word multisig; multisig needs to be added into the list in docs/book/spell-check-custom-words.txt

[luisburigo]

lgtm, but CI is failing on spellchecking the word multisig; multisig needs to be added into the list in docs/book/spell-check-custom-words.txt

done ✅

[sdankel]

Thank you!

[K1-R1]

🚀