[SPARK-42700][BUILD] Add h2 as test dependency of connect-server module

[LuciferYang]

What changes were proposed in this pull request?

Run the following commands

build/mvn clean install -DskipTests -pl connector/connect/server -am
build/mvn test -pl connector/connect/server

then we can see the following error message due to SPARK-42555 A adds the loading org.h2.Driver in beforeAll of ProtoToParsedPlanTestSuite, but

ProtoToParsedPlanTestSuite:
*** RUN ABORTED ***
  java.lang.ClassNotFoundException: org.h2.Driver
  at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:476)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589)
  at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
  at java.base/java.lang.Class.forName0(Native Method)
  at java.base/java.lang.Class.forName(Class.java:398)
  at org.apache.spark.util.Utils$.classForName(Utils.scala:225)
  at org.apache.spark.sql.connect.ProtoToParsedPlanTestSuite.beforeAll(ProtoToParsedPlanTestSuite.scala:68)
  at org.scalatest.BeforeAndAfterAll.liftedTree1$1(BeforeAndAfterAll.scala:212)
  at org.scalatest.BeforeAndAfterAll.run(BeforeAndAfterAll.scala:210)
  at org.scalatest.BeforeAndAfterAll.run$(BeforeAndAfterAll.scala:208)
  ...

So this pr add h2 as test dependency of connect-server module to make maven test pass.

Why are the changes needed?

Add h2 as test dependency of connect-server module to make maven test pass.

Does this PR introduce any user-facing change?

No

How was this patch tested?

manual check：

build/mvn clean install -DskipTests -pl connector/connect/server -am
build/mvn test -pl connector/connect/server

with this pr, all test passed

[LuciferYang]

cc @HyukjinKwon fix a maven test failed of connect server module due to dependency loss

[hvanhovell]

@HyukjinKwon @gatorsmile @cloud-fan @dongjoon-hyun this is the 101st we have broken the maven build in the last month alone. We don't test with it, but we do feel comfortable to release with it. Are we sure the dual build setup is still a thing we want to pursue? Isn't it time to start thinking about greener pastures...

[LuciferYang]

this is the 101st we have broken the maven build in the last month alone. We don't test with it, but we do feel comfortable to release with it. Are we sure the dual build setup is still a thing we want to pursue? Isn't it time to start thinking about greener pastures...

Personally, I think we should consider migrating the build to sbt only in Spark 3.5.0, also cc @pan3793

[hvanhovell]

LGTM

[dongjoon-hyun]

For the following @hvanhovell 's question, I'd ask @srowen 's advice.

this is the 101st we have broken the maven build in the last month alone. We don't test with it, but we do feel comfortable to release with it. Are we sure the dual build setup is still a thing we want to pursue? Isn't it time to start thinking about greener pastures...

[srowen]

While I'm a Maven person myself, I above all have also long preferred one build over two, and an SBT build is fine with me. I actually can't recall if there were strong reasons to keep one or the other in the past; seems like there were Reasons we needed both. We do use mvn in a few places in scripts to parse out stuff about the build, like to determine when new dependencies have been added. mvn and sbt dependency resolution aren't the same, but all the more reason to just pick one, even if we have to migrate some scripts

[LuciferYang]

re-triggered GA

[beliefer]

@LuciferYang Thank you for the job. #40291 need this one.

[HyukjinKwon]

Merged to master and branch-3.4.

[LuciferYang]

Thanks @HyukjinKwon @hvanhovell @dongjoon-hyun @srowen @beliefer