Handle client-Stats records

Handles client-Stats records which don't have a completion record.
This avoids building up a list of pending records and ultimately creating a panic.

New metric p4_cmds_paused_cumulative

Added metric and new entry for process table for log2sql

Release new resource pressure pause metric parsing

New metrics:

• p4_cmds_running
• p4_cmds_running_max
• p4_cmds_paused
• p4_cmds_paused_max
• p4_cmds_paused_errors
• p4_pause_rate_cpu
• p4_pause_rate_mem
• p4_pause_state_cpu
• p4_pause_state_mem

Parses lines such as:

2024/06/19 12:25:31 560465376 pid 1056102: Server is now using 55 active threads.
2024/06/19 12:25:31 560486548 pid 1056102: Server now has 10 paused threads.
2024/06/19 12:25:38 004246895 pid 1056103: Server under resource pressure.  Pause rate CPU 59%, mem 20%, CPU pressure 2, mem pressure 1

Detect commands being removed from monitor table properly

Errors were previously being spuriously added to pending list and causing stack issues.

Add new metrics: p4_prom_memory and p4_prom_build_info

• Tweak Makefiles for consistency and new arm targets
• Add new metric p4_prom_build_info
• Major test refactoring to clean JSON of 0 value fields before comparison
• Tweak memory calculations
• Add metric p4_prom_memory

v0.12.6

Don't sum computedLapse field entries as they may occur multiple times for a command - just update with latest value.

Handle p4d logs without completed records

• Handles logs where few or no completed records (configurable server=1 rather than server=3)
  • New parameter: --no.completion.records Set if log was generated with server=1 and thus no completion records expected.
• Tweak build system to work on Mac M3 (arm64)
• Add new pre-built targets

Fix bug with blank netbytesupdated field

Incorrectly being inserted in SQL.
Fixed some issues with p4locks and tidied its output.

Handle new memory and lbr entries in logs

Include comments in sqlite schema to help users.
Parse entries like:
--- memory cmd/proc 2404mb/2404mb
Also:
--- lbr Uncompress
--- opens+closes+checkins+exists 1+1+0+0
--- reads+readbytes+writes+writebytes 2+2.6K+0+0

Handle submit/populate mulit-line descriptions

It is possible to do a submit or populate like this:

p4 submit -d 'First line
Second line
'

And the results caused parse errors in the log. Now handled.