Introduce git_rebase to set up a rebase session

Introduce `git_rebase` to set up a rebase session that can
then be continued.  Immediately, only merge-type rebase is
supported.
git_reset: const the git_signature arg
Introduce git_rebase_abort

Abort an in-progress rebase and move the working directory and
repository back to the ORIG_HEAD state.
Introduce git_rebase_next

`git_rebase_next` will apply the next patch (or cherry-pick)
operation, leaving the results checked out in the index / working
directory so that consumers can resolve any conflicts, as appropriate.
git_rebase_next: write conflicts nicely during rebase
Introduce git_rebase_commit

Commit the current patch of a rebase process.
git_rebase_commit: drop already-picked commits

Already cherry-picked commits should not be re-included.  If all changes
included in a commit exist in the upstream, then we should error with
GIT_EAPPLIED.
git_rebase_next: test that we return GIT_ITEROVER
Introduce git_rebase_finish to complete a rebase
git_rebase_commit: write HEAD's reflog appropriately
Introduce `git_note_author`, `git_note_committer`
git_rebase_finish: rewrite notes when finishing rebase
git_rebase_next: provide info about the operation
rebase: init/open a git_rebase object
rebase: preload all operations
git_rebase: iterators for operations
rebase: oid member of operation should be const
rebase: clean up some warnings and memory leaks
s/git_merge_head/git_annotated_commit

Rename git_merge_head to git_annotated_commit, as it becomes used
in more operations than just merge.
rebase: updates based on PR comments