search by date range across date fields

[hkong-mitre]

This is a follow-up to #20 , #19 , and #5. It standardizes on the specific kinds of dates and date ranges that can be handled by the web search UI:

• when dates are specified, it will only search for dates in date fields. It will NOT search for the date string in any string fields since it cannot easily do date range processing on string fields. If this is important, we can implement this in a later sprint.
• all dates are referenced as ISO 8601 (UTC). To use local time, use the ±HH:MM method of time offset from UTC.
• The following 3 approaches are available in the web UI search:
  • A single date or date-time is converted to a date range:
    • YYYY-MM-DD -> 2025-10-10 is same as 2025-10-10..2025-10-10 which will return any CVEs with any date fields matching that day, disregarding any time components present in the record
  • A date range is specified by 2 dates or date-times, separated by ...
    • YYYY-MM-DD0..YYYY-MM-DD1 -> 2025-10-10..2025-10-11 returns all the CVEs in the 2 day period in the range
    • YYYY-MM-DDTHH:MM:SS.mmm0..YYYY-MM-DDTHH:MM:SS.mmm1 ->
      • 2025-10-10T00:00:00..2025-10-10T12:00:00 returns all the CVEs in the 12 interval (note that the hour, minute and second are all required, but the Z is optional and assumed to be there if missing)
      • 2025-10-10T12:30:00..2025-10-10T12:34:00Z returns all the CVEs in the 4 minute interval
      • 2025-10-10T12:34:00.500Z..2025-10-10T12:34:00.999Z returns all the CVEs in the 499 miliseconds interval