Python 3.12 introduced a new event monitoring system
`sys.monitoring`. This patch augments Numba's dispatcher so as to
emit events associated with a Python function starting and
returning from execution. Tools monitoring for such events will
therefore be able to identify execution of Numba's pure machine
code regions as though they were actual Python functions. This
allows tools such a ``cProfile`` to record Numba compiled function
execution and report them as part of their output.

Fixes numba#9289

Adds support to Numba's dispatcher for the ``sys.monitoring.events``
of type ``RAISE`` and `PY_UNWIND``. Associated unit tests are added
and cProfile testing is updated. Docs are updated to match.

Resolved conflicts:
	numba/tests/support.py

As title.

If a Numba function is being run under cProfile and the
function raises an exception, the dispatcher must handle
this correctly. It is not valid to call
`PyFrame_FastToLocals` without saving and restoring the
exception state across the call as it can clear the
exception state itself. This patch fixes this problem and
also stops calling `PyFrame_LocalsToFast` in Python 3.11
where the "whats-new" docs claim that the frames are now
looked after by the virutal machine.

Fixes some RST syntax and a couple of grammatical errors.

This works around a potential bug in CPython where the state
associated with a monitoring tool can "leak" in an unexpected
manner.

This patch also removes the use of the functools cache on the
generator for test functions, this to eliminate any potential
state being stored on the code objects associated with the
test functions.

As title.