Enterprise v3 duplicate point write ordering, workarounds, compaction timing

> 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 https://github.com/influxdata/docs-v2/issues/6584#issuecomment-3607611753_

Start with the Enterprise gen1-duration reference linked in the issue and compare it with the related discussion in issue 6584. Add the Enterprise-specific guidance about duplicate point ordering, workarounds, and compaction timing; done means the Enterprise documentation clearly covers the referenced behavior and setting.

Written by the indexing model from the issue text.