fix: Store validateArgs wrongfully overwriting start, end unix time

[paulheg]

When querying data before 1970-01-01 (UNIX time 0) validateArgs would set start to -in64 max and end to int64 max.

Closes #24669

Changes made:
Removed two faulty if statements.

• I've read the contributing section of the project README.
• Signed CLA (if not already signed).

[philjb]

@gwossum - if you have a moment, could you look at this potential bug fix from @paulheg? See the bug report for details. The PR does seem to have targeted the impact code where it is replacing any timestamp less than or equal to 0 aka 1970-01-01 with the smallest signed int (plus 2).

I think the code was intending to do this (similar issue for end)

	if start < models.MinNanoTime {
		start = models.MinNanoTime
	}

as math.MinInt64 and math.MinInt64 + 1 are apparently used as sentinels. @paulheg - I think you need to adjust your fix. Check out the comment on models.MinNanoTime.

This bug seems to be encountered only for queries looking before 1970 so it is rather unlikely to be encountered in the wild, except for @paulheg here!

• range() does not filter correctly depending on year #24669

[paulheg]

@philjb with the comment of models.MinNanoTime it makes a lot more sense what was going on there.
I updated the pr.

[paulheg]

I just added some tests to check this behaviour.

[paulheg]

Is there anything blocking us from merging this?
The builds are only failing because of timeouts downloading the dependencies.

[davidby-influx]

LGTM. Thanks for the contribution!

[davidby-influx]

Cherry-picked to #25146