Improve getOperations logic and validations

[Torres-ssf]

The getOperations function and all associated helper functions currently require refactoring and improvements in their logic.

1. For instance, there is a (potential) recurring issue where the operation variable is reassigned during each iteration of the loop, as can be seen in the following snippet:

fuels-ts/packages/providers/src/transaction-summary/operations.ts

Lines 317 to 323 in 3c1920e

	let operations: Operation[] = [];
	coinOutputs.forEach((output) => {
	const input = getInputFromAssetId(inputs, output.assetId);
	if (input) {
	const inputAddress = getInputAccountAddress(input);
	operations = addOperation(operations, {

It is crucial to ascertain whether this logic properly handles cases like a single transaction that involves the transfer of multiple assets among various addresses.

We can also improve the logic here and stop reassigning the operations variable if only one operation is expected.

2. Additionally, it is necessary to validate whether transactions of the Create type can in fact generate a Transfer Asset operation:

fuels-ts/packages/providers/src/transaction-summary/operations.ts

Lines 408 to 413 in 3c1920e

	if (isTypeCreate(transactionType)) {
	return [
	...getContractCreatedOperations({ inputs, outputs }),
	...getTransferOperations({ inputs, outputs }),
	];
	}

Proper validation will ensure the reliability and maintainability of this code.

[arboleya]

Completed via #1619.