Support postgres temporal features

**Is your feature request related to a problem? Please describe.**
In a lot of domains, you have values that are tracked over time ranges or schedules, where the natural key is an entity plus a time range.

**Describe the solution you'd like**[
Supporting postgres WITHOUT OVERLAPS and FOR PORTION OF](https://neon.com/postgresql/postgresql-19/temporal-data-operations)

**Describe alternatives you've considered**
Having a separate syntax for these. But just matching the postgres syntax is likely to allow supporting more applications.

**Additional context**
Exclusive ranges in a Btree are also useful in postgres since querying for the unique half closed interval that includes a time is easier than a GIS lookup. That part could end up being a pebble level range query optimization. But the data modeling side should just be at the SQL layer.

Jira issue: CRDB-63909

Epic CRDB-60817