[Feature request] Show arguments that were used for a pre-existing Transaction, in either CLI or Explorer context.

[Alexzander-Stone]

Feature

Many smart contracts are convoluted with the (type) arguments that are passed during TXN execution.

I suggest adding a feature that either (or both):

• Shows the parameter usage of an already-included TXN in the context of the run/view function from the module.
• Outputs the aptos move run command to run from the Aptos CLI, with the same arguments of an already-included TXN.

Reasoning

Today, one must go through the payload to determine which data was sent as arguments. Furthermore, new users tend to have issues with properly defining the data.

"Should I use string:["abc"] or string:abc or string:"abc" or some kind of vector when passing to the CLI or explorer parameter?" - common CLI user

By having this feature users will understand the proper formatting, without needing to resort to testing different permutations of inputs.