gh-35955: links for Python standard errors using class role in src/doc

<!-- ^^^^^
Please provide a concise, informative and self-explanatory title.
Don't put issue numbers in there, do this in the PR body below.
For example, instead of "Fixes #1234" use "Introduce new method to
calculate 1+1"
-->
<!-- Describe your changes here in detail -->

In `src/doc`, Let us use `:class:...Error` to make links to python's own
documentation

<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes #12345". -->
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->
<!-- If your change requires a documentation PR, please link it
appropriately -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
<!-- Feel free to remove irrelevant items. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- #12345: short description why this is a dependency
- #34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

URL: #35955
Reported by: Frédéric Chapoton
Reviewer(s): Matthias Köppe

Author: Release Manager

build/pkgs/configure/checksums.ini

@@ -1,4 +1,4 @@
 tarball=configure-VERSION.tar.gz
-sha1=354d134d4bcdedba55ed2bcb1eac6ea33146ca15
-md5=2143a40fdce9ed5cb8b29a6232be4789
-cksum=304076036
+sha1=556e5e5a03146223da4c540532f2744b5f020aae
+md5=43e504a3833767059afc054b8be73a1e
+cksum=3293099866

build/pkgs/configure/package-version.txt

@@ -1 +1 @@
-37fa2da8e75716793e91c384237a5e9f67ed83e8
+68e7d744a31fa469d9b2746353041faa409877d2

src/doc/de/tutorial/interactive_shell.rst

@@ -373,7 +373,7 @@ Fehlerbehandlung
 Wenn irgendetwas schief geht, werden Sie normalerweise eine
 Python-Fehlermeldung sehen. Python macht sogar einen Vorschlag, was den
 Fehler ausgelöst hat. Oft sehen Sie den Namen der Fehlermeldung,
-z.B. ``NameError`` oder ``ValueError`` (vgl. Python Library Reference
+z.B. :class:`NameError` oder :class:`ValueError` (vgl. Python Library Reference
 [PyLR]_ für eine komplette Liste der Fehlermeldungen). Zum Beispiel:
 
 .. skip

src/doc/en/faq/faq-usage.rst

@@ -115,7 +115,7 @@ issue these commands:
     import _tkinter
     import Tkinter
 
-If they do not raise an ``ImportError`` then it worked.
+If they do not raise an :class:`ImportError` then it worked.
 
 
 How do I import Sage into a Python script?
@@ -663,7 +663,7 @@ With objects a and b and a function f, I accidentally typed f(a) = b instead of
 It is because of how functions are defined in Sage with the
 ``f(x) = expr`` notation using the preparser. Also notice that if you
 make this mistake inside of an ``if`` statement, you will get a
-``SyntaxError`` before anything else goes wrong. So in this case,
+:class:`SyntaxError` before anything else goes wrong. So in this case,
 there is no problem.
 
 

src/doc/en/installation/source.rst

@@ -546,7 +546,7 @@ If
    sage: import _tkinter
    sage: import Tkinter
 
-does not raise an ``ImportError``, then it worked.
+does not raise an :class:`ImportError`, then it worked.
 
 .. _build-from-source-step-by-step:
 

src/doc/en/reference/coercion/index.rst

@@ -345,7 +345,7 @@ Methods to implement
     this case ``r * s`` gets handled as ``r._act_on_(s, True)`` or
     ``s._acted_upon_(r, False)`` and ``s * r`` as ``r._act_on_(s, False)`` or
     ``s._acted_upon_(r, True)``. There is no constraint on the type or parents
-    of objects passed to these methods; raise a ``TypeError`` or ``ValueError``
+    of objects passed to these methods; raise a :class:`TypeError` or :class:`ValueError`
     if the wrong kind of object is passed in to indicate the action is not
     appropriate here.
 

src/doc/en/thematic_tutorials/tutorial-programming-python.rst

@@ -176,9 +176,9 @@ indentation. Most of the time a new block is introduced by
 
   .. CODE-BLOCK:: python
 
-     raise <ErrorType> [, error message]
+     raise <ErrorType>[("error message")]
 
-  Usual errors include ``ValueError`` and ``TypeError``.
+  Usual errors include :class:`ValueError` and :class:`TypeError`.
 
 Functions
 =========

src/doc/en/tutorial/interactive_shell.rst

@@ -426,7 +426,7 @@ Errors and Exceptions
 When something goes wrong, you will usually see a Python
 "exception". Python even tries to suggest what raised the
 exception. Often you see the name of the exception, e.g.,
-``NameError`` or ``ValueError`` (see the Python Library Reference [PyLR]_
+:class:`NameError` or :class:`ValueError` (see the Python Library Reference [PyLR]_
 for a complete list of exceptions). For example,
 
 .. skip

src/doc/en/tutorial/tour_algebra.rst

@@ -16,7 +16,7 @@ functions are defined to be ``var(...)``. As an example:
     sage: diff(sin(u), u)
     cos(u)
 
-If you get a ``NameError``, check to see if you misspelled something,
+If you get a :class:`NameError`, check to see if you misspelled something,
 or forgot to define a variable with ``var(...)``.
 
 

src/doc/en/tutorial/tour_functions.rst

@@ -24,7 +24,7 @@ These functions can be plotted, but not differentiated or integrated.
        Graphics object consisting of 1 graphics primitive
 
 In the last line, note the syntax. Using ``plot(f(z), 0, 2)`` instead
-will give a ``NameError``, because ``z`` is a dummy variable in the
+will give a :class:`NameError`, because ``z`` is a dummy variable in the
 definition of ``f`` and is not defined outside of that definition.
 In order to be able to use ``f(z)`` in the plot command, ``z``
 (or whatever is desired) needs to be defined as a variable.  We