We intend to create one of the hydra-plutus scripts with aiken.

This separates the aiken build, which yields the plutus.json blueprint
and the haskell build which provides access to the compiled validators.

Instead of using the plutus-tx "compiledScript", we use the
loaded-from-blueprint aiken script in the init validator and when
constructing/observing transactions in the hydra-node.

This is not yet working and it does not correctly detect changes to plutus.json

Plutus-tx seems to be encoding tuples as a Constr on-chain.

Also add TODO comments for things that are missing to be removed.

… script info

By regenerating the plutus.json file using -k flag during aiken build.

This removes the need of using aiken/builtin function decode_utf8,
providing some small optimization.

Also recreated plutus scripts.

To correlate with the rest.

Also removed its golden spec.

Finally added a note about a fragility being present while accessing
the commit validator script from the blueprintJSON.

Seems like the aiken compiler uses plutus core version 1.1.0 syntax and
we need to declare it as a PlutusV3 script.

We do not need the plutus-style envelope and this would not match with
the PlutusV2 used there.

This will keep the first trace argument which we expect to see in our
mutation tests.

This does not require us to be in a git repository and hence makes the
test more flexible and isolated.

The hydra-plutus library seems to be consistently rebuilt when the
plutus.json gets changed.

This was failing with PPViewHashesDontMatch because the transaction was
referencing the commit script which is does not always need, and the
commit script being of different version than the other scripts spent.