DataSet::Value: specialise the bool case to use 8bit size bitfield

For this we specialise FileValue<bool> to use an "unsigned char"
as the boolean storage (instead of bool directly) and then translate
this to (via NATIVE_B8) to STD_B8LE hdf5 types.
This should close issue #185
DataSet: unify {file, mem}TypeForValue() to common function

The common function is the new h5_type_for_value_dtype()
Merge pull request #186 from gicmo/valueWriteBool

Special case bool when for Value IO
fixed invalid read valgrind problems in TestDimension
Merge pull request #187 from jgrewe/master

fixed invalid read valgrind problems in TestDimension

LGTM
[CMake] Specify library version (include ABI version)
[CMake] Properly version the shared-library
[CMake] Disable framework building (OSX only) for now
[CMake] Use install TARGETS instead of FILES to install the lib
Merge pull request #188 from gicmo/libVersion

Add project version to cmake and properly version the lib
fixed valgind problem in util::splitCompoundUnit
fixed valgrind problem in TestDataArray::testDimension()
Merge pull request #190 from jgrewe/valgrind_testDimension

Fixed valgrind problem in TestDataArray::testDimension()

LGTM
[test] testPolynomial: raise delta to 10e-10
[CMake] Version: Raise to 0.9.1
Merge pull request #189 from jgrewe/valgrind_TestUtil

fixed valgrind problem in util::splitCompoundUnit

LGTM
[CTest] Enable memcheck (valgrind) to travis/unix scripts

Valgrind (cf. issue #180) revealed a few subtle bugs. It seems like
a good idea to run valgrind all the time when doing CI.
[travis] Install valgrind
[CTest] Add quite option to valgrind (log is huge otherwise)
[test] Runner: Single test selection code changed to plug leaks

We now use the more sane method of passing the test we want
to execute to TestRunner::run() instead of finding the tests and
overwriting the variable with it, causing all but the selected test
to leak.