Redact compiledCode & hash in generated blueprint tests

The point of those tests is to ensure that blueprints are generated
  properly, irrespective of the generated code. It is annoying to
  constantly get those test failing every time we introduce an
  optimization or something that would slightly change the generated
  UPLC.

crates/aiken-lang/src/gen_uplc/builder.rs

@@ -365,11 +365,9 @@ pub fn find_introduced_variables(air_tree: &AirTree) -> Vec<String> {
             .cloned()
             .chain(snd_name.iter().cloned())
             .collect_vec(),
-        AirTree::PairAccessor { fst, snd, .. } => fst
-            .iter()
-            .cloned()
-            .chain(snd.iter().cloned())
-            .collect_vec(),
+        AirTree::PairAccessor { fst, snd, .. } => {
+            fst.iter().cloned().chain(snd.iter().cloned()).collect_vec()
+        }
         AirTree::PairClause {
             fst_name, snd_name, ..
         } => fst_name