Let a tracing test run slower to prevent div-by-zero crashes in line_profiler due to measured zero runtime.

Python 3.11 hid _PyLong_FormatAdvancedWriter and
_PyFloat_FormatAdvancedWriter. I've disabled USE_UNICODE_WRITER
for the moment but I suspect we want to find replacements in the longer term.

To silence a compiler warning since it was added in Python 3.11a2.

For 0.29.x branch only.

With reference to https://github.com/cython/cython/issues/4365#issuecomment-977023011
in Python 3 PyCode_NewEmpty does everything we need to set
exception traceback code objects.

This change is probably only a real improvement on Py3.11 onwards
(where the replacement for PyCode_new is currently pretty slow).
On earlier version it'll probably be fairly similar (maybe one extra allocation for the cline case?)

* Initial support for Python 3.11 (GH-4414)

https://github.com/cython/cython/issues/4414

* Add a basic replacement for PyCode_New().

An optimized versions would be nice, but this is intended to work sufficiently to start testing. Also, CPython 3.11 might actually add a new C-API function to simplify setting the current code position. That might be used instead.

* Disable introspection of frame object with vectorcall

This feature looked to only be used for early Python versions that don't have the full vectorcall protocol (and the contents of the frame object are changed in Python 3.11).

* Use new C-API function to get the current frame on Python 3.11 alpha (GH-4427)

Use the accessor function instead of the direct struct member (which is now the wrong type).

https://github.com/cython/cython/issues/4427
Closes https://github.com/cython/cython/issues/4416

* Fix number of arguments

* Disable CYTHON_FAST_PYCALL for 3.11 in Cython 0.29.x due to non-trivial incompatibilities.

* Remove remanent of 3.8alpha/beta workaround for PyCode_New().

All the versions we currently test are new enough that the alias is no longer necessary.

The string comparison was reporting '11' < '4' (so OpenMP tests were being skipped on GCC 11)

Fixes https://github.com/cython/cython/issues/3647

Use newer test dependencies in Py3.6+. (Excluding 3.10 for now to give the projects a bit more time.)

Disable some plain Python (non Cython related) tests that fail in Py3.10 due to changed error messages.

Avoid "possible loss of data" warning in MSVC by adding redundant casts to code that gets discarded later.

Still requires the more conservative __index__ here rather than a possibly
truncating __int__ because this is used in a context where floating point
values should probably be treated specially.

This fixes Github issue #2752.

Repair coverage tests to make them work with coverage 6.1, which changed the HTML output format that the tests parse.

See https://github.com/python/cpython/pull/28968/8e5de40f90476249e9a2e5ef135143b5c6a0b512
which is part of implementing
https://bugs.python.org/issue35134
moved the header "longintrepr.h" into a sub-folder.
The notes on this change suggested to include "Python.h" instead.

docs: Use the Cython + IPython lexers that come with Pygments to avoid having to maintain our own ones.

Instead of __Pyx_SetTracing(), Profile.c now uses PyThreadState_EnterTracing() and PyThreadState_LeaveTracing(), which were added to Python 3.11.0a2:
https://github.com/python/cpython/pull/28542

When these functions are used, Cython no longer sets directly PyThreadState.cframe.use_tracing.

"PyUnicode_CompareWithASCIIString()" does not raise exceptions and takes a "const char*" as argument.

This was causing c++ classes in if-statements to crash.
Fixes #4348

Avoid copying unaligned 16-bit values since some platforms require them to be aligned. Use memcpy() instead to let the C compiler decide how to do it.

Closes https://github.com/cython/cython/issues/4343

Make a helper function in a C++ test correctly propagate exceptions so that it won't have to spit out compiler warnings.