[SPARK-47097][CONNECT][TESTS][FOLLOWUP] Increase timeout to 1 minute for interrupt tag test

### What changes were proposed in this pull request?

This is a follow-up to increase `timeout` from `30s` to `1 minute` like the other timeouts of the same test case.
- #45173

### Why are the changes needed?

To reduce the flakiness more. The following is the recent failure on `master` branch.
- https://github.com/apache/spark/actions/runs/8944948827/job/24572965877
- https://github.com/apache/spark/actions/runs/8945375279/job/24574263993

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Pass the CIs.

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

No.

Closes #46374 from dongjoon-hyun/SPARK-47097.

Authored-by: Dongjoon Hyun <[email protected]>
Signed-off-by: Dongjoon Hyun <[email protected]>

Author: dongjoon-hyun

connector/connect/client/jvm/src/test/scala/org/apache/spark/sql/SparkSessionE2ESuite.scala

@@ -196,7 +196,7 @@ class SparkSessionE2ESuite extends RemoteSparkSession {
 
     // q2 and q3 should be cancelled
     interrupted.clear()
-    eventually(timeout(30.seconds), interval(1.seconds)) {
+    eventually(timeout(1.minute), interval(1.seconds)) {
       val ids = spark.interruptTag("two")
       interrupted ++= ids
       assert(interrupted.length == 2, s"Interrupted operations: $interrupted.")
@@ -213,7 +213,7 @@ class SparkSessionE2ESuite extends RemoteSparkSession {
 
     // q1 and q4 should be cancelled
     interrupted.clear()
-    eventually(timeout(30.seconds), interval(1.seconds)) {
+    eventually(timeout(1.minute), interval(1.seconds)) {
       val ids = spark.interruptTag("one")
       interrupted ++= ids
       assert(interrupted.length == 2, s"Interrupted operations: $interrupted.")