Support ledger parameters in tx command and deprecate/remove transaction_entry

[mDuo13]

Aside from #2597, the only advantage the transaction_entry command has over the tx command is that you can use it to query for a particular transaction in a single ledger version. Adding the standard ledger-lookup options (ledger_index & ledger_hash) to the tx method would make tx's proper functionality a strict superset of transaction_entry. After doing so, we could simplify the API by removing the transaction_entry method.

If the request specifies a ledger with ledger_index / ledger_hash (or maybe even the deprecated ledger field), the tx command should query only the specified ledger. If the requested transaction hash is not included in the specified ledger, the method should return a txnNotFound error.

[carlhua]

Consider this for API v2

[intelliot]

Low priority - postponing to api_version 3 (2024)