fix(golang): the guest's EQL round-trip test passes the expected context

The context_field change gave validate::record_tree and decrypt_record an
expected-context parameter. The test behind the guest's eql feature still
called both the old way, so `cargo test --all-features` on the guest did
not compile. Both calls pass None: the plan has a context of its own.

Author: coderdan

languages/golang/encrypt/guest/src/ops.rs

@@ -735,9 +735,9 @@ mod tests {
         assert_eq!(eql["hm"].as_str().unwrap().len(), 64);
 
         // Opens back through the EQL type's own decryption.
-        validate::record_tree(&sealed, &plan).expect("the tree fits");
+        validate::record_tree(&sealed, &plan, None).expect("the tree fits");
         let opened =
-            block_on(decrypt_record(Scope::Client(&cipher), &sealed, &plan)).expect("opens");
+            block_on(decrypt_record(Scope::Client(&cipher), &sealed, &plan, None)).expect("opens");
         let FfiValue::Object(values) = decode_value(&opened).expect("a value") else {
             panic!("an object")
         };