[SPARK-46259][PYTHON][DOCS] Add an appropriate link for error class usage documentation.

[itholic]

What changes were proposed in this pull request?

This PR proposes to add appropriate link for error class usage documentation.

Why are the changes needed?

The current Usage of Contributing Error and Exception documentation is lack of information where users exactly can search the existing error classes, and also where users can add a new error classes. We should add an appropriate link to make the documentation clearer.

Does this PR introduce any user-facing change?

No API changes, but this improves the usability of error class usage documentation:

Before

After

How was this patch tested?

Manually build docs and confirm.

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

No.

[itholic]

I have no idea what happened to continuous-integration/appveyor/pr, since I couldn't catch any clue for the current failure.
Let me just re-trigger the CI again.

[dongjoon-hyun]

+1, LGTM.

[dongjoon-hyun]

FYI, since Apache Spark 3.0.0, we don't allow . at the end of the PR title.

• [SPARK-28616][INFRA] Improve merge-spark-pr script to warn WIP PRs and strip trailing dots #25356

So, if you don't mind, please don't add . at the end of the PR title. Although the PR merge script is designed to be clean up like the following, it adds another extra step to the committers. 😄

$ dev/merge_spark_pr.py
git rev-parse --abbrev-ref HEAD
Which pull request would you like to merge? (e.g. 34): 44175
I've re-written the title as follows to match the standard format:
Original: [SPARK-46259][PYTHON][DOCS] Add an appropriate link for error class usage documentation.
Modified: [SPARK-46259][PYTHON][DOCS] Add an appropriate link for error class usage documentation

[dongjoon-hyun]

Merged to master. Thank you, @itholic .

[itholic]

So, if you don't mind, please don't add . at the end of the PR title

Oh, I see. Thanks for the notice!