Optimize transaction's graphql queries

[arboleya]

During some load tests, we realized a couple of issues (#3279, #3277) that we're fixing and optimizing.

In keeping with this theme, we should continue the effort and review our predefined GQL queries and fragments.

Every field removal is a breaking change and can break things for apps, so we need to be extra careful here.

Taking from the providers/operations.graphql:

• getTransaction
• getTransactionWithReceipts
• getTransactions
• getTransactionsByOwner
• getRelayedTransactionStatus

[petertonysmith94]

@Torres-ssf do you think this can be closed as part of #3336? I can't see any further optimizations.

[Torres-ssf]

Closing this issue as the optimizations have already been addressed through the following closed PRs:

• chore!: optimize getTransactions query #3336
• chore: optimize blockWithTransactions query #3309
• chore!: remove blockId in transaction list responses #3379
• feat!: read malleable fields from transaction status on subscription #2962