fix: only apply EN seal criteria checks on >=v29 protocol (#4491)

## What ❔

Only apply seal criteria checks through PanicSealer on >=v29 protocol

## Why ❔

Some older protocol versions had higher circuit (and maybe other) limits
that are no longer avilable in code constants

## Is this a breaking change?
- [ ] Yes
- [ ] No

## Operational changes
<!-- Any config changes? Any new flags? Any changes to any scripts? -->
<!-- Please add anything that non-Matter Labs entities running their own
ZK Chain may need to know -->

## Checklist

<!-- Check your PR fulfills the following items. -->
<!-- For draft PRs check the boxes as you complete them. -->

- [ ] PR title corresponds to the body of PR (we generate changelog
entries from PRs).
- [ ] Tests for the changes have been added / updated.
- [ ] Documentation comments have been added / updated.
- [ ] Code has been formatted via `zkstack dev fmt` and `zkstack dev
lint`.

Author: cytadela8

core/node/state_keeper/src/seal_criteria/conditional_sealer.rs

@@ -238,6 +238,7 @@ impl ConditionalSealer for NoopSealer {
 }
 
 /// Sealer for usage in EN. Panics if passed transaction should be excluded.
+/// Performs verification only from v29
 #[derive(Debug)]
 pub struct PanicSealer {
     sealers: Vec<Box<dyn SealCriterion>>,
@@ -293,6 +294,10 @@ impl ConditionalSealer for PanicSealer {
         tx_data: &SealData,
         protocol_version: ProtocolVersionId,
     ) -> SealResolution {
+        if protocol_version < ProtocolVersionId::Version29 {
+            // we do not validate seal criteria before v29. Appropriate constants are not available.
+            return SealResolution::NoSeal;
+        }
         tracing::trace!(
             "Checking seal resolution for L1 batch #{l1_batch_number} with {tx_count} transactions \
              and metrics {:?}",
@@ -317,7 +322,7 @@ impl ConditionalSealer for PanicSealer {
                     // no seal, don't need to do anything
                 }
                 SealResolution::ExcludeAndSeal => {
-                    panic!("Transaction should have been excluded, but was sequenced");
+                    panic!("Transaction from batch {}, tx_count {}, should have been excluded, but was sequenced due to sealer {}", l1_batch_number, tx_count, sealer.prom_criterion_name());
                 }
                 SealResolution::Unexecutable(reason) => {
                     panic!("Unexecutable transaction was sequenced: {reason:?}");

core/node/state_keeper/src/testonly/test_batch_executor.rs

@@ -288,7 +288,7 @@ impl TestScenario {
     /// Provided `SealManager` is expected to be externally configured to adhere the written scenario logic.
     pub(crate) async fn run_panic(self, sealer: Arc<dyn ConditionalSealer>, message: &str) {
         let join_error = self.run(sealer).await.expect_err("Not paniced");
-        let panic_message = join_error.into_panic().downcast::<&'static str>().unwrap();
+        let panic_message = join_error.into_panic().downcast::<String>().unwrap();
         assert!(panic_message.contains(message), "Different panic message");
     }
 }

core/node/state_keeper/src/tests/mod.rs

@@ -240,7 +240,7 @@ async fn panic_sealer_panic_scenario() {
         .batch_sealed("Batch 1")
         .run_panic(
             Arc::new(sealer),
-            "Transaction should have been excluded, but was sequenced",
+            "should have been excluded, but was sequenced due to sealer test_slots",
         )
         .await;
 }