API update: input argument renaming and potentially expansion of allowed input

[JeneaVranceanu]

What context is your feature request related to?

API update.

What solution would you like?

We have function that accept CodableTransaction data type by the name options. The name is old that was left from old days using TransactionOptions.

1. We must at least update that API by renaming options input arguments to transaction. Extracted as separate issue 787. Fixed in 786.
2. Documentation must be added to all functions that accept these transaction objects stating that the purpose is to give the ability to pass a prefilled transaction with values like nonce, gasLimit etc.
3. We must check for other APIs, e.g. ERCs we have implemented, to see if we need to add a similar transaction input argument. The reason for this could be: giving users the ability to configure the exact block, nonce, gasLimit etc. on each specific call. For read-only operations parameters like block are relevant.

Any additional context?

No response