Better, simpler fix than #250

Bootstrap fixes, including develop-eggs removal

Buildout no longer breaks on packages with non-ascii filenames in them.

Slightly improved version of lelit's #172

This means the eggs/ cache dir creation also moved to the start of buildout
instead of happening somewhere deep in the installation mechanism. I'll need
to adjust the test output for this.

Avoid prefixing buildout dir to 'special' rpath elements.

Noted the change in buildout's changelog, too, as that's much more prominent
and as it fixes a buildout bug.

Replaces #204, fixes #30.

A date leads to less confusion than a version number separate
from buildout's own version number. Similarly, tracking buildout's version
number leads to bootstraps with a new version number but without changes or to
bootstraps with version number from an already-older buildout. So: a date is
best.

I don't think many people use this option as it isn't documented.
It used to be handy around the time when we had lots of breakage.
Nowadays it isn't needed.
So... I'm moving it out of the way to make room for --version as a proper version-returning option.

This is an urelated change from mgedmin's #204 pull request.
Prefixing is good as it might help figuring out what keeps filling up a temp
dir in case there's a problem.

See #86 and #222

Travis speed improvement through caching

The [:] is necessary to edit the os.walk results in-place. Otherwise the
filtering-out of .svn, CVS and so doesn't work as intended.
(Note: this regression I put in was caught by one of the tests! Good that
we've got such a large amount of tests!)

Added fs_to_text() function that ensures a filename is always unicode (python
2) or str (python 3).

os.walk() gets such a unicode dirname as start point, so that it tries to do
its best on python2. The resulting filenames are converted to unicode to make
really sure that the join() doesn't fail with a decoding error.

The input to the hash function is encoded, as it gives an ascii encoding error
otherwise on python 2.

There is code in buildout to remove develop-eggs that it knows about.
So if everything is OK, develop-egg removal works fine.
If there's something fishy goign on, however, buildout
doesn't clean it up enough. Zapping the entire directory upon bootstrap
is a very effective way to prevent problems.

Reason: the old osc.recipe.sysegg did add develop-eggs .egg-link files to the
site-packages dir, effectively short-circuiting buildout's picked versions.
Likewise an old bootstrap could have left a setuptoos.egg-link to an ancient
setuptools version. I just this minute had to help a colleague with just such
a problem.

The only effect of the import is that ez_setup's use_setuptools() function
does a sys.exit(2) when the required version doesn't match the site package's
one.

If the import doesn't happen, use_setuptools() will just grab a matching
version if the site package's version is too old.

Note that the latest ez_setup.py scripts default to requiring the very latest
setuptools version! So --allow-site-packages isn't really very useful this
way.