Add PlutusV3 conformance tests and also control budgets

There were some odd discrepancy for `integerToByteString` on the mem
  side. Either 1 or about 1000 mem units off; which I couldn't quite
  figure out. Yet, it proves useful to validate builtin at large and
  ensure we have a valid cost model for v3.

crates/uplc/test_data/conformance/v2/example/overapplication/overapplication.uplc

@@ -0,0 +1,19 @@
+(program
+  1.0.0
+  [
+    [
+      [
+        [
+          [
+            (force (builtin ifThenElse))
+            [ [ (builtin lessThanInteger) (con integer 1) ] (con integer 3) ]
+          ]
+          (builtin addInteger)
+        ]
+        (builtin subtractInteger)
+      ]
+      (con integer 1)
+    ]
+    (con integer 3)
+  ]
+)

crates/uplc/test_data/conformance/v2/example/overapplication/overapplication.uplc.budget.expected

@@ -0,0 +1,2 @@
+({cpu: 864540
+| mem: 1704})

crates/uplc/test_data/conformance/v2/example/overapplication/overapplication.uplc.expected

@@ -0,0 +1 @@
+(program 1.0.0 (con integer 4))