v0.52.3

• Collector log output: Reduce frequency of some snapshot log events
  • Previously, near real-time "compact" snapshots would generate log lines
    every 10 seconds, which made errors hard to find
  • Now, a single log line is printed once a minute with a summary of snapshots
    submitted
  • Note that --verbose will still log every snapshot as it's submitted
• Collector log output: Add "full" prefix for full snapshots sent every 10 minutes
  • This changes the "Submitted snapshot successfully" message to read
    "Submitted full snapshot successfully" instead
• OpenTelemetry integration:
  • Support pganalyze tracestate to set start time of the span
  • Start time can be specified with t member key as Unix time in seconds,
    with decimals to specify precision down to nano seconds
  • This allows specifying a better span start and end time in case precise
    timestamps are not present in the Postgres logs, like with Amazon RDS
• Allow pg_stat_statements failures and continue snapshot processing
  • Previously, when pg_stat_statements data collection failed (e.g. a timeout
    when the query text file got too large), the whole snapshot was treated as
    failed and only reported an error snapshot to pganalyze, without any
    statistics
  • Instead, treat pg_stat_statements errors as a collector error in the
    snapshot, but continue afterwards and report other statistics that were
    collected successfully