migrate tracing from PrestoDB

[jerryleooo]

Description

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

This is a new feature that supports tracing in Trino.

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

This mainly adds tracer along with the query, so some interfaces and dependencies are changed. Actually this mainly borrowed from PrestoDB.

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

With a tracer along with the query, we can understand the time spent in each stage, so easier for us to find the potential performance bottleneck.

Related issues, pull requests, and links

#1826
#2010
#4207
#9924
#11157

Documentation

( ) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
(x) 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:

# Section
* Adding tracer along with queries. ({issue}`11244`)

[martint]

Thanks for your contribution. However, we have other plans to add tracing support with OpenTelemetry instead of the approach proposed here. By using OpenTelemetry, we get better integrations with a vast ecosystem of observability tools.

[martint]

Thanks for your contribution. However, we have other plans to add tracing support with OpenTelemetry instead of the approach proposed here. By using OpenTelemetry, we get better integrations with a vast ecosystem of observability tools.