Label the reaper thread

This enables identifying those threads when analyzing a GHC event log
file using ghc-events-analyze.
Make sure the reaper thread can always be killed

Previously the reaper thread would be unkillable if createPool was
called in a masked context i.e.:

  pool <- mask_ $ createPool ...

When pool gets garbage collected the KillThread exception can't be
delivered to the reaper thread because it inherited the masked state of
the calling thread.

This could lead to a resource leak.

Now we use: forkIOWithUnmask $ \unmask -> unmask ...

which ensures asynchronous exception can always be delivered to the
reaper thread.
Merge pull request #17 from basvandijk/label-reaper-thread

Label the reaper thread
Require at least base-4.4.0.0 (ghc-7.2.1)

This is the first base which provides: forkIOWithUnmask
Make developer flag manual