Implement getReadTimeNanos for JdbcRecordCursor

[posulliv]

Description

Implement the getReadTimeNanos method in JdbcRecordCursor so that physicalInputReadTime will represent how long was spent reading data.

This will also show up in a in EXPLAIN ANALYZE VERBOSE output for scans on JDBC connectors. For example, with this change a TableScan operator against a MySQL table shows physical input read time in connector metrics:

 Fragment 1 [SOURCE]
     CPU: 44.27ms, Scheduled: 73.26ms, Blocked 0.00ns (Input: 0.00ns, Output: 0.00ns), Input: 1503 rows (281.36kB); per task: avg.: 1503.00 std.dev.: 0
     Output layout: [custkey, name, address, nationkey, phone, acctbal, mktsegment, comment, dummy_col]
     Output partitioning: SINGLE []
     TableScan[table = mysql:junk.customer junk.customer]
         Layout: [custkey:bigint, name:varchar(255), address:varchar(255), nationkey:bigint, phone:varchar(255), acctbal:double, mktsegment:varchar(255
         Estimates: {rows: 1483 (517.02kB), cpu: 517.02k, memory: 0B, network: 0B}
         CPU: 43.00ms (100.00%), Scheduled: 71.00ms (100.00%), Blocked: 0.00ns (?%), Output: 1503 rows (281.36kB)
         connector metrics:
           'Physical input read time' = {duration=5.20ms}

Is this change a fix, improvement, new feature, refactoring, or other?

Minor improvement.

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

How would you describe this change to a non-technical end user or system administrator?

Related issues, pull requests, and links

Documentation

( X) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

() No release notes entries required.
(x) Release notes entries required with the following suggested text:

# ClickHouse, Druid, MariaDb, MySql, Oracle, PostgreSQL, Redshift, SingleStore, SQL server, Phoenix
* Report wall time spent reading data from JDBC sources. ({issue}`13132`)

[raunaqmorarka]

lgtm % comment

[colebow]

Would it be reasonable to put this release note in the JDBC driver section rather than all of the JDBC-based connectors?

[raunaqmorarka]

Would it be reasonable to put this release note in the JDBC driver section rather than all of the JDBC-based connectors?

This is not related to the Trino JDBC driver. It's about JDBC-based connectors reporting the wall time spent in reading data from the external system to the engine so that it can be shown in EXPLAIN ANALYZE VERBOSE, web ui and reported to the event listeners.

[findepi]

JdbcRecordCursor is part of JDBC-based connectors
and it's not part of JDBC driver (the two things are independent)