Different results with different time ranges after write line protocol

Steps to reproduce:
Let's say you have datapoints starting on the 9th of December 2022.
1. Now you add new datapoints before the 9th of December 2022 with line protocol.
For example:
XXXXXXXXXX pvenergytoday=1.3 1668945814
(where XXXXXXXXXX is your _measurement)
Write this line with precision selected as seconds into the database.

2. After successfully writing this line to the database, open the data explorer and select the _measurement XXXXXXXXXX and the _field pvenergytoday as well as a time range from a date before the newly written data point and todays date.

3. You will only see the newly written data point(s) but not the data points beginning on the 9th December and afterwards.

4. Now select a time range with a start date after the newly written data point but before the 9th of December and today, now you will see all the data points beginning on the 9th December until today.

Expected behavior:
After writing a datapoint as mentioned above and selecting a time range from before the newly written data point until today, the newly written data point and all the existing data points beginning from the 9th of December until today should be listet/shown.

Actual behavior:
Depending on the data range selection you can only see the newly written data point or the existing data points but not both at the same time-

Environment info:
GOSU_VER: 1.12
InfluxDB v2.6.1
Influx CLI v2.6.1
Using docker image influxdb:2.6.1-alpine.

Config:
Default Config

Reproduce the report in the InfluxDB 2.6.1 Alpine Docker environment using the line protocol write and Data Explorer time ranges described above. Compare results when the range starts before versus after the newly written point; done means both the new point and the existing points from December 9 onward appear together for the broader range.

Written by the indexing model from the issue text.