(Boost) Add include <path> to EDG and backend CLI (--with-boost=<path>)

This addresses an issue reported by Rice University. My error report
to them after investigation:

```
It looks like some of the errors are related to a possible mis-match in
Boost versions.

For example,

    test2013_241.C [err]: /usr/include/boost/mpl/apply.hpp:138:31: error:
missing binary operator before token "("

This test is using "/usr/include/boost", however ROSE was configured to
use Boost from "/projects/pkgs/boost".
```

The problem is that the ROSE/configure --with-boost=<path> is not
being added to the EDG or backend compiler commandlines. It's peculiar
that this ever worked because it turns out that Rice's /usr/include
version of Boost is 1.33.1, which is the same for our RHEL5 machines
in Jenkins.

The mysteries of software development continues...
(BOOST) Add Boost version info to ROSE --version

Define two new utility functions that return Boost
version information:

  rose_boost_version_id()    Numeric version, e.g. 10470
  rose_boost_version_path()  Path to installation, e.g. /usr/

Add this Boost version information to the --version output:

  version_message()
Merge branch 'master' of rosecompiler1.llnl.gov:rose/edg4x/rose
Merge branch 'master' of rosecompiler1.llnl.gov:rose/edg4x/rose
(BOOST) Patch CMake to quote the ROSE_BOOST_PATH
(decl move)
* declararation rescoping : skip compiler generated code from system headers.
* handle single statement for-loop body, and similar bodies of while, if, etc.
* Relax getLoopIndexVariable(), return NULL instead assert false
* SageInterface::ensureBasicBlockAsFalseBodyOfIf() and changeAllBodiesToBlocks(): add a flag to allow avoiding creation of empty body
Merge branch 'master' of rosecompiler1:rose/edg4x/rose
(Binary Analysis) Working around a gcc-4.2.4 optimization bug
Merge remote branch 'rc/master' into m68k
(Binary Analysis) Include "rose.h" in a test