Allow passing custom inputs when evaluating UPLC code

[nielstron]

The command aiken uplc eval <input> does currently not support passing any values. This is quite cumbersome, as usually programs evaluate to lambda expressions that are meant to be executed on i.e. PlutusData.

I suggest to extend the CLI to allow the following aiken uplc eval <input> (<uplc code>)* where the optional additional code evaluates to values that are passed to the program stored in <input>.
Example: aiken uplc eval sc.uplc "(con data #02)".

An alternative is to parse data more dynamically like it is done by pluto (example pluto usage pluto eval sc.pluto 2 -> this automatically generates the above PlutusData object, a tagged integer)