fix(filter)!: keep a short time fraction and read the zone after the fraction

[pdevito3]

For later consideration in a major version. Do not merge now. #134 restored the v1.14.2 fraction rules to keep v1.x compatible (restore commit b49ad2b). This PR re-applies the break parts of 5c84ef6. The captain decides on this PR separately.

Summary

• DateTimeFormatParser reads the zone only after the fraction: date, time, fraction, zone.
• A quoted TimeOnly value keeps every fraction digit, like an unquoted value. The rightIsQuotedLiteral argument of CreateRightExpr is removed, because no other code uses it there.

v1.14.2 behavior (and main)

• The date and time parser accepts the zone before the fraction: 2024-01-15T08:00:00Z.5 parses.
• A quoted time uses the milliseconds only when the fraction has 3 or more digits, and the microseconds only when it has 6 or more. "08:30:00.5" and "08:30:00.50" compare with 08:30:00.

New behavior

• The zone comes after the fraction, like ISO 8601. An unquoted value with the zone before the fraction throws ParsingException.
• A quoted time keeps its fraction: "08:30:00.5" is 08:30:00 and 500 milliseconds.

Main already accepts these and they do not change: a fraction before the zone, 7 fraction digits, an unquoted time fraction, and a time list.

Example

FilterParser.ParseFilter<TestingPerson>("""Time == "08:30:00.5" """);
FilterParser.ParseFilter<TestingPerson>("SpecificDateTime == 2024-01-15T08:00:00Z.5");

• v1.14.2 and main: the first filter matches 08:30:00, not 08:30:00.500. The second filter parses.
• This PR: the first filter matches 08:30:00.500. The second filter throws ParsingException.

Justification

.5 is half a second. A filter that drops it gives wrong rows without an error. A zone before the fraction is not an ISO 8601 format, and the README shows only ISO 8601 values.

Migration

• Write the zone after the fraction: 2024-01-15T08:00:00.5Z.
• A caller that wrote a short fraction and expected the whole second must remove the fraction.

README

The date and time format list now tells that a time fraction keeps every digit, and that the zone comes after the fraction.

Tests

These tests come back from main before #134:

• Unit FilterParsingRegressionTests.fractional_seconds_are_kept: the cases Time == "08:30:00.5" and Time == "08:30:00.50" expect the fraction again. The v1.14.2 cases Z.5, +02:00.500, and "08:30:00.500" are removed.
• Unit quoted_time_with_fewer_than_three_fraction_digits_drops_the_fraction is removed. It held the v1.14.2 behavior.
• Integration FilterParsingRegressionTests.fractional_second_value_matches_by_its_fraction -> fractional_seconds_are_kept (Postgres, a quoted .5 matches the fraction row again).

New unit test: zone_before_the_fraction_throws (2 cases).

dotnet build: 0 warnings, 0 errors. dotnet test: 401 unit tests and 281 Postgres integration tests (Testcontainers) pass, 0 failures.

[pdevito3]

This PR had two breaking changes. Two PRs replace it, one change in each PR:

• fix(filter)!: read the zone of a date and time value only after the fraction #165: the zone of a date and time value comes after the fraction.
• fix(filter)!: keep a short fraction of a quoted time #166: a quoted time keeps a short fraction.

I close this PR. The captain decides on each new PR separately.