[SPARK-48961][PYTHON] Make the parameter naming of PySparkException consistent with JVM

[itholic]

What changes were proposed in this pull request?

This PR proposes to make the parameter naming of PySparkException consistent with JVM

Why are the changes needed?

The parameter names of PySparkException are different from SparkException so there is an inconsistency when searching those parameters from error logs.

SparkException:

spark/common/utils/src/main/scala/org/apache/spark/SparkException.scala

Lines 27 to 33 in 6508b1f

	class SparkException(
	message: String,
	cause: Throwable,
	errorClass: Option[String],
	messageParameters: Map[String, String],
	context: Array[QueryContext] = Array.empty)
	extends Exception(message, cause) with SparkThrowable {

PySparkException:

spark/python/pyspark/errors/exceptions/base.py

Lines 29 to 40 in 6508b1f

	class PySparkException(Exception):
	"""
	Base Exception for handling errors generated from PySpark.
	"""
	def __init__(
	self,
	message: Optional[str] = None,
	error_class: Optional[str] = None,
	message_parameters: Optional[Dict[str, str]] = None,
	query_contexts: Optional[List["QueryContext"]] = None,
	):

Does this PR introduce any user-facing change?

The error parameter names are changed from:

• error_class -> errorClass
• message_parameters -> messageParameters
• query_contexts -> context

How was this patch tested?

The existing CI should pass

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

No.

[itholic]

cc @HyukjinKwon

[HyukjinKwon]

LGTM if tests pass

[itholic]

Merged into master. Thanks!