Include lifted versions of common libraries

One that jumps to mind: directory, though there are plenty of others. There are some design points in here:
- Do we use `MonadIO` (more commonly used) or `MonadBase IO` (used by lifted-base)
- When providing functions with IO in negative position, when do we use `MonadBaseControl` and when do we use `MonadCatch`/`MonadMask`. Proposal: use `MonadCatch`/`MonadMask` whenever possible (i.e., exceptions) and `MonadBaseControl` otherwise (e.g., `timeout`).

The issue names directory and the MonadIO, MonadBase IO, MonadBaseControl, MonadCatch, and MonadMask abstractions, but no files or tests. Start by surveying the existing library set and the directory package, then resolve which constraint strategy applies to each function. Done means an agreed scope and API for lifted common libraries, with corresponding implementations and tests.

Written by the indexing model from the issue text.