feat(sql): allow list of timestamps of higher precision than required in alter table attach/detach/drop partition

[marregui]

Closes #2879

The approach is to let the compiler only process the chars required to understand a partition dir name, while ignoring the rest, for each of the items in the comma separated list following the LIST token.

Example, for a table partitioned by month:

alter table x drop partition list '2023-03-29T23', ... ;

2023-03-29T23 is a valid partition name now for month granularity because the compiler knows that the patter for partition by month is yyyy-MM, which means it can parse a date up to month, thus -29T23 is ignored. Incidentally, this would work too alter table x drop partition list '2023-03-a-banana' ;. We are trying to make life easier for users who might use a full timestamp (select max(ts) from table) to drop a partition (the last one in this example).

WHERE is not supported, no value, and harder a problem to solve.

The case of partition by week is complicated. We first try to parse the partition name candidate with format YYYY-Www, and if it fails we assume the user sent a string that looks more like a date, or a timestamp, and we parse it with the day pattern yyyy-MM-dd, then we translate it to the timestamp of the day the week starts at.

[puzpuzpuz]

Thanks for implementing this feature!

[ideoma]

[PR Coverage check]

😍 pass : 78 / 80 (97.50%)

file detail

	path	covered line	new line	coverage
🔵	io/questdb/cairo/PartitionBy.java	49	51	96.08%
🔵	io/questdb/griffin/engine/functions/date/WeekOfYearFunctionFactory.java	12	12	100.00%
🔵	io/questdb/std/datetime/microtime/TimestampFormatUtils.java	10	10	100.00%
🔵	io/questdb/griffin/SqlCompiler.java	7	7	100.00%