As the include file is located in the same application, using
-include instead of -include_lib removes the need for the
code directory to be called "lager" or "lager-VSN".

The micro-benchmarks show up to 20x improvement, which further
reduces logging overhead.

Helps with pattern matching.

I didn't want the lager_log_message record being used across application
boundaries, this will insulate other applications from any changes to
the message type's internal structure.

Various bugs uncovered during this testing were fixed and added to the
test suite.

Had to add a pseudo-ternary operator to the formatter to support this.
Also allowed lager:log to log metadata.

Also removed commented out code.

There are still differences between the erlang io_lib and the trunc_io in
how ~p/~P are handled, but a first step is useful here.

Whenever we have the filename we ALWAYS have the module name, which is
effectively just as useful and already printed.

Tests now pass on both R15B and R14B03.

Thanks for Kostis for helping me figure this one out

This is just silly busy-work since they're library applications, but
whatever.

Additional changes and formatting by Andrew Thompson

Bitstrings are binaries that don't end on an 8 bit boundary, so dealing
with the trailing bits is annoying. Thanks to the bit_size bif we don't
have to resort to io_lib for printing them.