Support for more precise time formats

[ConorMurphy21]

Is your feature request related to a problem? Please describe.
I have a log format with: "timestamp-format": [ "%Y-%m-%d %H:%M:%S.%f" ]. This works in theory but due to maybe the limitation of storing the log_time with only 3 bits of precision e.g. "SS.SSS" instead of the 6 from my logs some functionality is wonky.

:hide-lines-before here, and :hide-lines-after here will sometimes hide lines way before or after the current cursor position
:goto may also act imprecisely if I copied a timestamp from some other time format

The most important issue though is that when collating logs from multiple sources it's possible for logs to be out of order, I found an example of this when scanning my logs:

file1─2024-11-25 12:20:19.418361 0 ⋮, ⋮ "bar"                               │
file2┌2024-11-25 12:20:19.418207 1 ⋮, ⋮ "foo"

Describe the solution you'd like
The ideal solution would be to store datetime objects with a higher precision in database and hopefully that would solve all of these problems.

Describe alternatives you've considered
Another workaround idea / maybe useful anyways would be to allow formats to describe a collate order. I.e. after timestamp, what fields should be ordered next when merging log files. In this case my log has an "uptime field", which is a very precise floating point, which could be used to collate the logs (as a secondary criteria to timestamp). Though this doesn't solve some of the wonkyness with the timestamp based commands.

Thanks for any help with this issue. Overall after finding this tool I've been super happy and impressed with it!

[tstack]

Thanks for filing this, I failed to re-evaluate the memory layout for the data structure that stores information about log lines in recent years (lnav is quite old at this point). I'll fix things up to get this working better.