This extends git_repository_init_ext further with support for
initializing the repository from an external template directory
and with support for the "create shared" type flags that make a
set GID repository directory.

This also adds tests for much of the new functionality to the
existing `repo/init.c` test suite.

Also, this adds a bunch of new utility functions including a
very general purpose `git_futils_mkdir` (with the ability to
make paths and to chmod the paths post-creation) and a file
tree copying function `git_futils_cp_r`.  Also, this includes
some new path functions that were useful to keep the code
simple.

The extended version of repository init adds support for many
of the things that you can do with `git init` and sets up
structures that will make it easier to extend further in the
future.

In looking at PR #878, I found a few small bugs in the diff code,
mostly related to work that can be avoided when processing tree-
to-tree diffs that was always being carried out.  This commit has
some small fixes in it.

API for managing in-memory ignore rules

This fills out the ignore API and adds tests.

This creates a public API for adding to the internal ignores
list, which already existing but was not accessible.

This adds the new default value for core.excludesfile also.

Filemode enum

Avoids getting ERROR_SHARING_VIOLATION on win32
and killing the entire clar run.

Make the memory-window conrol structures global

Up to now, the idea was that the user would do all the operations for
one repository in the same thread. Thus we could have the
memory-mapped window information thread-local and avoid any locking.

This is not practical in a few environments, such as Apple's GCD which
allocates threads arbitrarily or the .NET CLR, where the OS-level
thread can change at any moment.

Make the control structure global and protect it with a mutex so we
don't depend on the thread currently executing the code.

Handling of 100664 deprecated mode in tree entries

Clone

Minor fixes

Return -1 to stop the iteration instead of not-0

git_tree_walk callback return value semantic does not match documentation

Fix message prettify length check

If you want to be absolutely safe with git_message_prettify, you
can now pass a NULL pointer for the buffer and get back the number
of bytes that would be copied into the buffer.

This means that an error is a non-negative return code and a
success will be greater than zero from this function.

git_note_foreach: Fix documentation for notes_ref parameter

git_note_oid: Fix the documentation to reference parameters using the correct names

git_note_create: Copyediting on documentation for the oid parameter

Fix incorrect array size in example for git_config_get_mapped

Config file parser includes = in name if no space around it

Returning a negative cancels the walk, and returning a positive one
causes us to skip an entry, which was previously done by a negative
value.

This allows us to stay consistent with the rest of the functions that
take a callback and keeps the skipping functionality.

However, there should be a way to cancel the walk and another to skip
the entry.

Okay, this is probably cleaner and it is also less net change
from the original version

This makes the message prettify buffer length check accurate.

The config file parser was not working right if there was no
whitespace between the value name and the equals sign.  This
fixes that.