OPLogConvert: Add support for Overo logs

These logs are different because they use the timestamped UAVTalk
message type (https://github.com/TauLabs/TauLabs/wiki/UAVTalk-Protcol)
and don't include the standard logging header (4 bytes timestamp
and 8 byte datasize).

I also had to parameterize the settings for the timestamp as it
goes from a 4 byte uint32 to 2 byte uint16.

Work on #277
OPLogConvert: Process wraparounds within the matlab code

This is especially problematic for the UAVTalk timestamping where
the timestamp is uint16 in ms and wraps around more frequently.
This required adding a lookup table for which objects are single
instance since that moves the location of the timestamp.

Work on #277
OPLogConvert: Handle multiple instance UAVOs from Overo

This is a little tricky because the relative position of the
instanceID field moves relative to the data for timestampped
UAVTalk packets.

Work on #277
OPLogConvert: Add overo flag to calling API
LogConvert: Verify that there are enough bytes to read the header

Since reading the header information isn't within the try catch we
should verify there are enough bytes.
LogConvert: Rename from OPLogConvert to LogConvert
Matlab logging: consistently use tabs
Logging: Change default filename to TauLabs-%DATE%
Merge pull request #277 from peabody124/overo_log_parsing

OPLogConvert support for Overo