fix(tesseract): drop SQL snapshot from FK-aggregate regression test

The SQL string captured by `build_sql(..)` differs between local and CI
environments: when `--features integration-postgres` is on and Docker is
available, `try_execute_pg` runs a second template-rendering pass that
emits CTE-wrapped SQL; the single-pass `build_sql` output is the
inline-subquery form. Same code, different rendering pipelines reachable.

The cubesqlplanner suite convention is to snapshot postgres execution
results (226 such files in the repo), not SQL strings (1 file — this one).
Drop the SQL snapshot to follow convention. The structural tautology
scanner above stays — it's the bug-specific, environment-independent
guard. The existing `assert_snapshot!(result)` on row data continues to
verify end-to-end correctness when CI's postgres container is up.

Author: tlangton3

rust/cubesqlplanner/cubesqlplanner/src/tests/integration/multi_fact.rs

@@ -547,8 +547,6 @@ async fn test_multiplied_aggregate_filtered_count_on_pk() {
         cursor = on_end;
     }
 
-    insta::assert_snapshot!(sql);
-
     if let Some(result) = ctx.try_execute_pg(query, SEED).await {
         insta::assert_snapshot!(result);
     }