test(fixtures): run the public-input tamper test on the base-commit path

The suite split put `tampered_public_input_is_rejected` in
`challenge_soundness_suite!`, so it only ran on `GoldilocksEfField` and the
base-commit witness path lost its dedicated public-input tamper test. It uses
`squaring_chain` and `two_public_inputs` and carries no
`Embedding<Target = Base<P>>` bound, unlike the two tests it was grouped with,
so it belongs in `soundness_suite!`.

Moving it back gives `GoldilocksField` both halves of the public-input pair: the
hash-guard rejection and the binding-covector rejection.

Author: BornPsych

tooling/provekit-fixtures/tests/shared/mod.rs

@@ -452,6 +452,11 @@ macro_rules! soundness_suite {
             $register();
             $crate::shared::public_input_binding_mismatch_is_rejected::<$field>();
         }
+        #[test]
+        fn tampered_public_input_is_rejected() {
+            $register();
+            $crate::shared::tampered_public_input_is_rejected::<$field>();
+        }
     };
 }
 
@@ -460,11 +465,6 @@ macro_rules! soundness_suite {
 #[macro_export]
 macro_rules! challenge_soundness_suite {
     ($field:ty, $register:path) => {
-        #[test]
-        fn tampered_public_input_is_rejected() {
-            $register();
-            $crate::shared::tampered_public_input_is_rejected::<$field>();
-        }
         #[test]
         fn tampered_challenge_is_rejected() {
             $register();