Bunyan

- [issue 103] `bunyan -L` (or `bunyan --time local`) to show local time.
Bunyan log records store `time` in UTC time. Sometimes it is convenient
to display in local time.

- [issue 205] Fix the "The Bunyan CLI crashed!" checking to properly warn of
the common failure case when `-c CONDITION` is being used.

- [issue 210] Export `bunyan.nameFromLevel` and `bunyan.levelFromName`. It can
be a pain for custom streams to have to reproduce that.

- [issue 100] Gracefully handle the case of an unbound
`Logger.{info,debug,...}` being used for logging, e.g.:

myEmittingThing.on('data', log.info)

Before this change, bunyan would throw. Now it emits a warning to stderr
*once*, and then silently ignores those log attempts, e.g.:

bunyan usage error: /Users/trentm/tm/node-bunyan/foo.js:12: attempt to log with an unbound log method: `this` is: { _events: { data: [Function] } }

- [issue 184] Fix log rotation for rotation periods > ~25 days. Before this
change, a rotation period longer than this could hit [the maximum setTimeout
delay in node.js](https://github.com/joyent/node/issues/8656). By Daniel Juhl.

- Drop the guard that a bunyan Logger level must be between TRACE (10)
and FATAL (60), inclusive. This allows a trick of setting the level
to `FATAL + 1` to turn logging off. While the standard named log levels are
the golden path, then intention was not to get in the way of using
other level numbers.

- [issue 178, 181] Get at least dtrace-provider 0.3.1 for
optionalDependencies to get a fix for install with decoupled npm (e.g. with
homebrew's node and npm).

- [issue 157] Restore dtrace-provider as a dependency (in
"optionalDependencies").

Dtrace-provider version 0.3.0 add build sugar that should eliminate the
problems from older versions:
The build is not attempted on Linux and Windows. The build spew is
*not* emitted by default (use `V=1 npm install` to see it); instead a
short warning is emitted if the build fails.

Also, importantly, the new dtrace-provider fixes working with node
v0.11/0.12.