[SPARK-53068][SQL][TESTS] Mark TransformWith*Suite as SlowSQLTest in sql/core

[dongjoon-hyun]

What changes were proposed in this pull request?

This PR aims to move TransformWith*Suite tests from sql - other tests pipeline to sql - slow tests pipeline for rebalancing the test workload and avoiding the AS-IS GitHub Action test timeout (120m).

$ find sql/core -name 'TransformWith*Suite.scala'
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithStateClusterSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithMapStateSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithStateUnsafeRowSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithStateChainingSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithStateAvroSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithStateSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithStateInitialStateSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithListStateTTLSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithValueStateTTLSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithMapStateTTLSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/streaming/TransformWithListStateSuite.scala
sql/core/src/test/scala/org/apache/spark/sql/execution/python/streaming/TransformWithStateInPySparkStateServerSuite.scala

Why are the changes needed?

This PR reduces sql - other tests running time from 101 mins to 84 mins.

BEFORE

• https://github.com/apache/spark/actions/runs/16678827879
  • sql - other tests: 101 mins
  • sql - slow tests: 57 mins

AFTER

• https://github.com/dongjoon-hyun/spark/actions/runs/16682057228/job/47222881995
  • sql - other tests: 84 mins
• https://github.com/dongjoon-hyun/spark/actions/runs/16682057228/job/47230513154
  • sql - slow tests: 66 mins

Does this PR introduce any user-facing change?

No because this is a test change.

How was this patch tested?

Pass the CIs with the rebalanced tests.

Was this patch authored or co-authored using generative AI tooling?

No.

[dongjoon-hyun]

Could you review this GitHub Action test rebalancing PR, @huaxingao ?

[dongjoon-hyun]

All tests passed.

[huaxingao]

LGTM

[dongjoon-hyun]

Thank you so much, @huaxingao . 😄