This is a common gotcha for new users who name their .pyx file after the C file that they want to wrap.
Closes https://github.com/cython/cython/issues/4177

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

When compiling pyarrow with cython 3.0 we get an error about the copy constructor of an object has been deleted on the generated context switch code.

Also make the "cpp_temp_assignment" test only run in C++11 since it is based on `std::move()`.

The condition wasn't triggering so code wasn't being tested (). This applies to:
```
def f(vector[double] x):
  pass
```
which should now generate:
```
__pyx_v_a = __pyx_convert_vector_from_py_double(values[0]); if (unlikely(PyErr_Occurred())) __PYX_ERR(0, 5, __pyx_L3_error)
...
__pyx_r = __pyx_pf_4cnvt_f(__pyx_self, __PYX_STD_MOVE_IF_SUPPORTED(__pyx_v_a));
```

I haven't included any specific tests because I think it should be covered by the existing test-suite (now that it works) and it's only a performance improvement - it doesn't allow any new behaviour.

See https://github.com/cython/cython/issues/4163

(Tried the "pattern" argument to loadTestsFromModule() in the unittest module, but it's not always taken into account, so manual selection is what works.)

Disable "cycoverage" test job since it currently fails, probably dude to issues with the "Cython.Coverage" plugin.

Add a coverage test job with a compiled Cython package to compare plain Python and compiled Cython both for completeness and speed.

Exclude end-to-end tests from test runs with '--cython-only' since they execute arbitrary test code.

This commit fixes a crash of Cython when generator expressions are used in cdef functions in pure python mode.
Closes https://github.com/cython/cython/issues/3477

The implementation of __Pyx__PyNumber_Float() wasn't checking whether
errors occurred on the calls to __Pyx_PyUnicode_AsDouble(),
__Pyx_PyBites_AsDouble(), and __Pyx_PyByteArray_AsDouble(). Errors from
those functions were now properly propagated to the caller.

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

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

Disable some unicode fstring tests for the debugging (f"{...=}") feature since unicode strings come out as "u'...'" in Py2.

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

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

The problem seems to be that __Pyx_CallUnboundCMethod0 optimizes the call incorrectly. This patch avoids it getting sent to that mechanism.