fix: only classify setUp as test setup if it has no parameters (#13204)

Contracts with `setUp(bytes memory)` (common in Gnosis Safe/Zodiac modules)
were incorrectly classified as dev/test contracts and excluded from
`forge build --sizes` output.

Now `setUp` is only classified as a test `Setup` function when it has no
parameters, matching Forge's actual test setup behavior.

Fixes #11126

Author: mattsse

crates/common/src/traits.rs

@@ -175,7 +175,7 @@ impl TestFunctionKind {
                 Self::InvariantTest
             }
             _ if name.starts_with("table") => Self::TableTest,
-            _ if name.eq_ignore_ascii_case("setup") => Self::Setup,
+            _ if name.eq_ignore_ascii_case("setup") && !has_inputs => Self::Setup,
             _ if name.eq_ignore_ascii_case("afterinvariant") => Self::AfterInvariant,
             _ if name.starts_with("fixture") => Self::Fixture,
             _ => Self::Unknown,
@@ -285,3 +285,18 @@ impl<T: std::error::Error> ErrorExt for T {
         alloy_sol_types::Revert::from(self.to_string()).abi_encode().into()
     }
 }
+
+#[cfg(test)]
+mod tests {
+    use super::*;
+
+    #[test]
+    fn test_setup_classification() {
+        // setUp() with no params should be classified as Setup
+        assert_eq!(TestFunctionKind::classify("setUp", false), TestFunctionKind::Setup);
+
+        // setUp(bytes memory) with params should NOT be classified as Setup
+        // This is common in Gnosis Safe/Zodiac modules
+        assert_eq!(TestFunctionKind::classify("setUp", true), TestFunctionKind::Unknown);
+    }
+}