For some reason, the diff for distutils/_backport/misc.py makes it seem
like it?s a new file instead of showing the changes I did during the
merge.

This moves individual backported functions from compat into a new
_backport.misc module.  compat regains its original purpose of
containing 2to3 support code (i.e. compat for projects using distutils2,
not internal compat for d2 code) and all backports now live under the
private _backport subnamespace.

Also fix the definition of ?any? to bind it to the builtin in 2.5+
(fsencode and detect_encoding not changed, they never exist in
2.x).

This should help avoiding issues like #13170.

Because of implicit relative imports, _backport.tarfile already imported
shutil from the backports instead of the stdlib; I have inlined the only
function it needed to remove the circular dependency between these
modules.

This codebase is compatible with 3.1, 3.2 and 3.3.  It was converted with 2to3
and a semi-automated diff/merge with packaging in 3.3 to fix some idioms.
We?ve now come full circle from 2.x to 3.x to 2.x to 3.x again :)

Starting from now, contributors can make patches for packaging (preferred, as
the stdlib?s regrtest is very useful), distutils2 or distutils-python3, and
we?ll make patches flow between versions.

The PEP 376 implementation used to live in d2._backport.pkgutil, which
was actually a mixed back/forward-port like sysconfig, so its tests were
in d2._backport.tests.test_pkgutil and the needed file in the same
directory.  Now the code lives in d2.database and the files in
d2/tests.)