The previous patch failed to update the expected number of op_codes,
which would result in an exception when creating an instance of
RemoteProgress. This patch corrects the value to the new expected number
of op_codes (8)

When running a long running operation (such as a clone on a large repo),
Git may return a message indicating that it is 'Finding sources'. Since
there is no bit field value for this message, this causes a large amount
of error messages to be emitted to stderr.

This patch fixes this by adding another bit field value for this
message, FINDING_SOURCES. Derived classes can look for this op_code and
handle it appropriately.

Do not swallow non-zero exit status during push and fetch unless
we managed to parse head information.

This behaviour will effetively handle cases were no work was done
due to invalid refspecs or insufficient permissions.

Fixes #271

When pushing/pulling, we ignore errors unless it's exit code 128.
The reason for this is now made explicit to make clear that issues
are handled by PushInfo flags accordingly.

Related #271

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

The latter happened as now BadName is thrown, instead of BadObject.
Changes.rst was marked accordingly

Previously, the implementation would gladly reset new commits in submodules,
and/or reset a dirty working tree.

Now the new force_reset/force flag has to be specified explicitly to get back
to the old behaviour.

All submodule tests except for one are working.

Assured unicode values are supported when reading the configuration,
and when getting author/committer information from the environment.

Fixes #237

Fixes #7

[ci skip]