Issue #407

I really never want to touch python again, and never deal with
py2/3 unicode handling anymore.
By now, it seems pretty much anything is better.
Is python to be blamed for it entirely ?
Probably not, but there are better alternatives.
Nim ? Rust ? Ruby ?
Totally

This issue only surfaced in python 2, in case paths containing unicode
characters were not actual unicode objects.

In python 3, this was never the issue.

Closes #331

When expanding directories, check if it is a symlink and don't expand
them at all.

Previously, we followed symlinks and expanded their contents, which
could lead to weird index files.

Fixes #302

It turned out that the index is not actually corrupted, which is good
news. What happens is that `git` writes `TREE` extension data into the
index, which causes it to write out the given tree *as is* next time
a `git commit` is executed. When using `git add`, this extension data
is maintained automatically. However, GitPython doesn't do that ... .
Usually this is no problem at all, as you are supposed to use
`IndexFile.commit(...)` along with `IndexFile.add(...)`.

Thanks to a shortcoming in the GitPython API, the index was
automatically written out whenever files have been added, without
providing control over whether or not *extension data* will be
written along with it.

My fix consists of an additional flag in `IndexFile.add(...)`, which
causes extension data not to be written by default, so commits can be
safely done via `git commit` or `IndexFile.commit(...)`.

However, this might introduce new subtle bugs in case someone is
relying on extension data to be written. As this can be controlled
through the said flag though, a fix is easily done in that case.

Fixes #265

However, it doesn't reproduce on the latest version of GitPython.
Maybe it's on an older one.

Previously, it checked for AssertionErrors, now we have to implement
need-unbare-repo check ourselves.