[influxdb3-enterprise] ingester logs an ERROR about snapshot sequence seeds on a clean start

A freshly installed cluster logs this once, on the first ingester start:

```
ERROR influxdb3_pacha_tree::ingest::unified_buffer::ingest: snapshot sequence
seeds disagree between the gen0 catalog and the manifest listing; allocating
above both gen0_last=None chain_last=Some(0)
```

Seen on 3.11.2 with file object storage on kind. The pod reaches 1/1 and writes and queries work, so this looks harmless, but it is logged at ERROR on an empty catalog where there is nothing to disagree about.

Raising it here because `.github/workflows/patterns.txt` greps install logs for error patterns, and because an ERROR on a clean install is what customers open tickets about. May belong upstream rather than in the chart.

Start with .github/workflows/patterns.txt to see how install logs are checked, then reproduce a clean install on kind and inspect the first ingester startup logs. Trace whether the chart can address the ERROR or whether it belongs upstream; done means the ownership and an actionable fix or escalation are documented.

Written by the indexing model from the issue text.