Test encoded on-chain code

[rynoV]

• We need to double check that the on-chain code has been encoded correctly. Try to construct some invalid transactions and see if the contracts fail as expected.
• Once we confirm that the contracts are properly encoded, it may be worthwhile to add some fixture tests for what the applied contracts should look like for some given arguments, to protect against changes to how arguments are applied by CTL.

[rynoV]

As of 5aecc5a (see #22), CNFT mint policy fails as expected with:

{"EvaluationFailure":{"ScriptFailures":{"mint:0":[{"validatorFailed":{"error":"An error has occurred:  User error:\nThe machine terminated because of an error, either from a built-in function or from an explicit use of 'error'.","traces":["UTxO not consumed","PT5"]}}]}}}

When I attempt to create a transaction that doesn't spend the utxo the script is parameterized with.

[rynoV]

The locking script (the other one that I added but wasn't sure about) was encoded in the same way as the CNFT mint policy so it's probably fine as well.

[samuelWilliams99]

We could attempt to set up CI to verify this - using a known private key wallet. However, running this against public testnet is very cleanroom. Perhaps plutip makes an appearance?