* add DRY gitdocs execution into #gitdocs_command and name the wrapper
  methods consistently
* remove some unnecessary calls to abs_current_dir when asserting
  output
* make the pid_file and gitdocs binary paths absolute so they are not
  affect by the setting of the current directory
* consolidate the #before_setup and #after_teardown methods
* replace #git_clone_and_gitdocs_add with #gitdocs_create, which
  eliminates some extra code and more more through the gitdocs CLI
  which makes the integration test more consistent

DRY the duplicate from the units tests for fabricating and making
assertions about git repositories.

Add GitFactory.append in the process.
Remove methods from the integration/test_helper which are no longer
used.

I think that will be useful, particularly for finding errors in Travis.
On a test failure the log file and the current aruba directory will be
printed.

The verbose flag will increase the log level to DEBUG, which will also
additional debugging logs to be added to the code, but hidden during
normal operations.

Now that the --verbose flag exists to increase log level, I think that
this is a more accurate name for this flag.

Add logging methods to Gitdocs to reduce method chains, and update the
existing log calls to best specify appropriate log levels.

...the notifications will be logged even if the notifications
themselves are not being displayed.

Because the HOME directory is reset for these tests git would not use
an existing global configuration. Write the user.name and user.email
into the testing home directory, so valid value will be present when
committing during the integration tests.