Enterprise v3 duplicate point write ordering, workarounds, compaction timing

[jstirnaman]

This is related for Enterprise v3:

InfluxDB v3 Enterprise uses the same underlying write semantics, so the non-determinism with duplicate points in the same batch can occur there as well. The difference is that Enterprise gives you more control over how long data stays in the “gen1” tier before being compacted/flushed via the gen1-duration setting:

https://docs.influxdata.com/influxdb3/enterprise/reference/config-options/#gen1-duration

Thanks @will-influxdata! I'll add it for Enterprise in a separate PR.

Originally posted by @jstirnaman in #6584 (comment)