This PR adds support for fetching `TIME_NS` values as instances of
`java.time.LocalTime` class, example:

```java
LocalTime lt = rs.getObject(1, LocalTime.class);
```

Nanosecond precision is maintained on fetching. Currently there is not
possible to preserve nanosecond precision for `TIME_NS` query
parameters.

The support is necessary to fix `test_all_types` failures introduced by
duckdb/duckdb#20361.

This PR adds support for fetching `TIME_NS` values as instances of
`java.time.LocalTime` class, example:

```java
LocalTime lt = rs.getObject(1, LocalTime.class);
```

Nanosecond precision is maintained on fetching `TIME_NS` values from DB.

Currently it is not possible to preserve nanosecond precision when
inserting `TIME_NS` values using query parameters.

The support is necessary to fix `test_all_types` failures introduced by
duckdb/duckdb#20361.

This PR adds support for fetching `TIME_NS` values as instances of
`java.time.LocalTime` class, example:

```java
LocalTime lt = rs.getObject(1, LocalTime.class);
```

Nanosecond precision is maintained on fetching `TIME_NS` values from DB.

Currently it is not possible to preserve nanosecond precision when
inserting `TIME_NS` values using query parameters.

The support is necessary to fix `test_all_types` failures introduced by
duckdb/duckdb#20361.

Add support for TIME_NS (see
duckdb/duckdb#20361).

The original PR added support for the `TIME_NS` type, which represents
the time of day in nanoseconds:
* Arrow supports this type
* Pandas does not have this type itself (but can handle it as an
`object` through arrow)
* Python does not have an equivalent - `datetime.time` has microsecond
precision.

Note that DuckDB supports `TIME_NS` -> `TIME` casting but not the other
way around, meaning that you can't insert e.g. a `datetime.time` into a
`TIME_NS` column.

This PR updates submodules and adds a number of minor changes:

 - update `duckdb` submodule to the latest `v1.5-variegata`
 - update `extension-ci-tools` submodule to the latest `main`
 - update `MainDistributionPipeline.yml` to the same versions of the
   engine and CI tools as above
 - update `Linux.yml` to set `LOCAL_EXTENSION_REPO` env var that is now
   (after some recent `unittest` chage) is required to run tests with
   extensions that are not statically linked (otherwise
   `require postgres_scanner` fails)
 - apply patch `getdatainternal.patch` from the engine repo
 - add a change to `postgres_storage.cpp` to accomodate to changes added
   in duckdb/duckdb#20508
 - update `attach_types.test` that started failing due to
   duckdb/duckdb#20361 change

PS: due to changes required for duckdb/duckdb#20508 it is suggested to
add `v1.4-andium` branch to this repo (on a current `main`).

TIME_NS Support + Arrow (duckdb/duckdb#20361)
No catalog found Nightly test fix (duckdb/duckdb#20409)
Avoid frequent checkpoints triggered by optimistic insertions (duckdb/duckdb#20336)