Allow to use results of `view` functions as action inputs

[wannabehero]

I imagined that we can define inputs for shortcuts not only by name: type as we do now, but also name: <view_function_result>.

<view_function_result> is another action that points to the contract and accepts arguments, but selects a view or pure function from the contract. It can also reference another view_function.

Before executing an action, all inputs should be resolved. Right now it works for ETH value and ENS names – view functions should work in a similar fashion: making an RPC call to set a value.