(Frontend) Remove extra #include
(CLI) (Darwin) Add initial support for -dylib_file

The Darwin linker supports this commandline option:

    -dylib_file <something>:<something>

Though I have not found any detailed description in
documentation.
(CLI) Fix handling of -I processing to allow space between argument

This commit allows a user to specify the header file include path
option in either of these two standard formats:

    1)  -I<path>    No space separating option and argument

    2)  -I <path>   Space(s) separating option and argument

Current CLI processing assumes that there is no space, case #1. So
when ROSE CLI processing encounters case #2, ROSE ends up treating
the <path> argument as binary source file.

This error occurred with this commandline:

    ```bash
    $ identityTranslator -I/some/header/path -print-libgcc-file-name -rose:verbose 3
    ...
    ######################### Inside of CommandlineProcessing::generateSourceFilenames() ############################
    CommandlineProcessing::isExecutableFilename(): name = /some/header/path validExecutableFileSuffixes.size() = 2
    sourceFileList = = /some/header/path
    ...
    ```

Which failed, rather than successfully outputting the GCC library
(as this commit fixes):

    ```bash
    $ identityTranslator -I/some/header/path -print-libgcc-file-name
    /path/to/gcc/lib/gcc/x86_64-unknown-linux-gnu/4.4.5/libgcc.a
    ```

NOTE: WARN if <path> argument does not exist. This cannot be FATAL
since most build systems will contain -I options with invalid paths,
for a variety of reasons.

Conflicts:
	src/frontend/SageIII/sage_support/sage_support.cpp
(KeepGoing) Refactor Signal Handling into keep_going.[h,cpp]

* Refactor KeepGoing support into separate files to reduce the
  clutter in the core of ROSE.

* Adopt policy for setting error codes:

  Set error code(s) local to the failing function. In the case
  of KeepGoing exception/signal handling, the caller becomes
  responsible for setting the failure code(s).

* Set global variable to toggle the KeepGoing feature:

    ROSE::KeepGoing:g_keep_going

  We #define these convenience macros:

      * KEEP_GOING_CAUGHT_FRONTEND_SIGNAL
      * KEEP_GOING_CAUGHT_FRONTEND_SECONDARY_PASS_SIGNAL
      * KEEP_GOING_CAUGHT_BACKEND_UNPARSER_SIGNAL

  Signal/exception handling must be added wherever a loop
  over all the files occurs. This allows us to capture the
  overall status of ROSE processing if multiple files are
  provided.

* Disable AstPerformance processing

  ROSE usually segfaults in AstPerformance processing when
  ROSE is run in -rose:keep_going mode. Therefore, we will
  "disable" AstPerformance processing when KeepGoing is enabled.

(KeepGoingTranslator)

* Add new CLI options for reporting:

     --report-fail    File reporting ROSE failures
     --report-pass    File reporting ROSE successes

* Add new output format to include error codes:

     ss << filename << " "
         << file->get_frontendErrorCode() << " "
         << file->get_unparserErrorCode() << " "
         << file->get_backendCompilerErrorCode() << " "
         << file->get_unparsedFileFailedCompilation();