Add proper `startTime` and `endTime` fields that use time instead of `short`

[bronwyncombs]

Is your feature request related to a problem? Please describe.

The Collecting Information startTime and endTime fields, described as "Start/End time in military format." in our schema, are short/java.lang.short field type.

The accepted entires for short fields must be whole numbers between -32768 and 32768. Meaning, what should be valid Start and End Time values, e.g., 18:00, 10:30, 12:54, aren't accepted.

The DwC eventTime term (http://rs.tdwg.org/dwc/terms/eventTime) is defined as "The time or interval during which a dwc:Event occurred."

• Notes: Recommended best practice is to use a time of day that conforms to ISO 8601-1:2019.
• Examples:
  • 14:07-06:00 (at or after 2:07pm and before 2:08pm in the time zone six hours earlier than UTC)
  • 08:40:21Z (at or after 8:40:21am and before 8:41:22am UTC)
  • 13:00:00Z/15:30:00Z (at or after 1pm and before 3:30pm UTC) |

Describe the solution you'd like
Change the startTime and endTime field types to a string or text field that allows a : character.

Reported By
Father Saturnino Urios University

[grantfitzsimmons]

Lot's of challenges changing these fields given historical usage, but worth considering as a new field eventTime, and perhaps also startEventTime and endEventTime that follow this format.