Make deployContract method a non-blocking call

[Torres-ssf]

The deployContract method in the ContractFactory currently submits the transaction and waits for it to be processed. This synchronous approach can lead to significant delays, as transaction processing times in a blockchain environment often take several seconds.

Having this method always act as a blocking call is impractical for real-world blockchain environments as it forces developers to wait for transaction completion before proceeding with other tasks.

The deployContract method should only wait for the TX to be processed if the user explicitly chooses to do it. This non-blocking approach should be the default behavior, as blocking the UI is not what users usually desire.

similar to #2492

[arboleya]

Are we talking about adding the awaitExecution flag as a new parameter?

fuels-ts/packages/contract/src/contract-factory.ts

Line 164 in dc17b9c

awaitExecution: true,

[Torres-ssf]

@arboleya Yes, we will also need to change the method's response type.

Currently, it returns an instance of the Contract class, ready to be used. This is only possible because the method waits for the transaction to be processed.

The ideal approach would be to have the deployContract method simply submit the transaction and return something that can be used to fetch the transaction, such as its ID or an instance of TransactionResponse. This way, dApp applications wouldn't get blocked when submitting the TX, and they would receive the transaction ID as a response, making it possible to attach hooks to fetch its status.