[SPARK-35672][FOLLOWUP][TESTS] Add more exclusion rules to MimaExcludes.scala for Scala 2.13

[sarutak]

What changes were proposed in this pull request?

This PR adds more MiMa exclusion rules for Scala 2.13.
#34649 partially resolved the compatibility issue but additional 3 compatibility problems are raised.

$ build/sbt clean
$ dev/change-scala-version.sh 2.13
$ build/sbt -Pscala-2.13 clean
$ dev/mima

...
[error] spark-core: Failed binary compatibility check against org.apache.spark:spark-core_2.13:3.2.0! Found 3 potential problems (filtered 910)
[error]  * synthetic method copy$default$8()scala.collection.mutable.ListBuffer in class org.apache.spark.executor.CoarseGrainedExecutorBackend#Arguments has a different result type in current version, where it is scala.Option rather than scala.collection.mutable.ListBuffer
[error]    filter with: ProblemFilters.exclude[IncompatibleResultTypeProblem]("org.apache.spark.executor.CoarseGrainedExecutorBackend#Arguments.copy$default$8")
[error]  * synthetic method copy$default$9()scala.Option in class org.apache.spark.executor.CoarseGrainedExecutorBackend#Arguments has a different result type in current version, where it is Int rather than scala.Option
[error]    filter with: ProblemFilters.exclude[IncompatibleResultTypeProblem]("org.apache.spark.executor.CoarseGrainedExecutorBackend#Arguments.copy$default$9")
[error]  * the type hierarchy of object org.apache.spark.executor.CoarseGrainedExecutorBackend#Arguments is different in current version. Missing types {scala.runtime.AbstractFunction10}
[error]    filter with: ProblemFilters.exclude[MissingTypesProblem]("org.apache.spark.executor.CoarseGrainedExecutorBackend$Arguments$")
...

Why are the changes needed?

To keep the build stable.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Confirmed MiMa passed.

$ build/sbt clean
$ dev/change-scala-version.sh 2.13
$ build/sbt -Pscala-2.13 clean
$ dev/mima

[sarutak]

@dongjoon-hyun Thank you for letting me know this issue! After I cleaned my repository and ran dev/mima, I observed this issue too.

[dongjoon-hyun]

Does this also come from SPARK-35672?

[sarutak]

Yeah, I think so.The parameter list of the case class Arguments was changed (userClassPath was removed) in SPARK-35672, which caused the class hierarchy of the class $Arguments$.

$ javap core/target/scala-2.13/classes/org/apache/spark/executor/CoarseGrainedExecutorBackend\$Arguments\$.class 
Compiled from "CoarseGrainedExecutorBackend.scala"
public class org.apache.spark.executor.CoarseGrainedExecutorBackend$Arguments$ extends scala.runtime.AbstractFunction9<java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.Object, java.lang.String, scala.Option<java.lang.String>, scala.Option<java.lang.String>, java.lang.Object, org.apache.spark.executor.CoarseGrainedExecutorBackend$Arguments> implements java.io.Serializable {

[SparkQA]

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49915/

[SparkQA]

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49915/

[SparkQA]

Test build #145443 has finished for PR 34664 at commit d20b841.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[sarutak]

Merging to master. Thank you @dongjoon-hyun for the review !