Wrap and implement submitAndAwaitStatus at provider level

[danielbate]

Since #3101, we have used the submitAndAwaitStatus subscription in SDK to submit transactions and poll it's result as part of a TransactionResponse.waitForResult(). This way we package both the transaction and the response for the consumer.

We should expose a more raw version of this endpoint like we do with other operations (simulate, dryRun, getBlobs etc) that still assists with the submission of the request but less heavy lifting with the response. This should reduce friction for consumers with obtaining the results of the subscription.

The expected API will look like so:

const txRequest = await wallet.createTransfer(wallet.address, 100_000);
const response = await provider.sendAndAwaitStatus(txRequest);
// { status: 'success', transactionId: '0x...', receipts: [] }

Ideally the response should use the outcome of #3536.

[danielbate]

Right now I think we should only do this for the provider, accounts have their own considerations and this is simply providing a slight abstraction over that subscription endpoint.

[danielbate]

Closed by #3541