* cache the bound method of _trace on self

this speeds up pure python tracing because we don't have to re-create a
bound method object all the time

* optimize checking whether a file should be traced

the optimization works based on the following heuristic: in a
majority of cases, functions call other functions in the same file. In
that situation we don't have to re-check whether we should trace the
file

* fix optimization in the presence of contexts

* fix too long line

use the python >= 3.7 feature of being able to disable line tracing by
setting the frame attribute f_trace_lines to False. This can be used for
the frames of functions that we aren't collecting coverage information
for (eg those functions in the stdlib).

This speeds up the pure python tracer in CPython by ~9x and in PyPy by
80% on a coverage run of one realistic project that I tried.

Version 3.11.0a4 introduced RESUME, so returns and calls are different now.
This change also fixes some mishandling of yield-from in previous releases.

The pyexpat bug that plagued us was fixed in Python 3.4:
https://bugs.python.org/issue22462

We no longer need the code that adapted to it.  The test will remain, couldn't
hurt.

Coverage.py predates sets as a built-in data structure, so the file data
collection has long been dicts with None as the values.  Sets are
available to us now (since Python 2.4 in 2004, which coverage.py dropped
support for in 2014!), we use sets.