Accept transactions by ID in pooledUserCommands

[mrmr1993]

This allows pooledUserCommands to accept transactions encoded with either hashes or ids, to make them more consistent with transactionStatus.

This also can be used to get the hash of a transaction from its ID via GraphQL: you can send the transaction as an ID and query its hash in the output.

Checklist:

• Document code purpose, how to use it
  • Mention expected invariants, implicit constraints
• Tests were added for the new behavior
  • Document test purpose, significance of failures
  • Test names should reflect their purpose
• All tests pass (CI will check this if you didn't)
• Serialized types are in stable-versioned modules
• Does this close issues? List them:

Closes #8244

[bkase]

!approved-for-mainnet