Add Protobuf 'any' type support to Kafka connector

[adamjshook]

Description

This adds support for the any Protobuf data type, converting the message type to JSON. The default implementation uses the ProtobufUtils mechanism for parsing the Descriptor. There is a separate implementation that uses Confluent's ProtobufSchemaProvider which is used instead when the ConfluentModule is enabled and uses caching when accessing the types.

This PR needs user-facing documentation which will be added as another commit.

Additional context and related issues

The Protobuf any type contains two fields, one type_url field and another being any serialized Protobuf message. The type_url is expected to be a URL that resolves to a serialized descriptor of the message. This change uses a java.net.URL of the type_url to open a stream and read the bytes of the descriptor which is then converted into a Descriptor object. We then pass this to a JSON printer to serialize the message. Afterwards, we have to sort all of the keys, including nested keys, as the Trino JSON type expects all keys to be ordered.

This requires users to ensure that the URL is resolvable from the Coordinator and Worker hosts, either by being a locally installed file:// on each machine or a remote https:// service.

Expands on #16836 which added oneof support

Release notes

( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
(X) Release notes are required, with the following suggested text:

# Kafka Connector
* Added support for reading Protobuf messages containing the `Any` Protobuf type. This is disabled by default and can be enabled by setting `kafka.protobuf-any-support-enabled` to `true`. Please see docs for more details.

[hashhar]

lgtm % cache auto-refresh behaviour

[hashhar]

if the ordering is relevant please add a commmment why. copy the one from sorted method in this class?

[hashhar]

hmmm, IMO the cache shouldn't refresh automatically by default

[adamjshook]

Updated to remove a configurable cache and instead use a non-evictable cache with a max size of 1000.

[adamjshook]

@mosabua Could you please review the documentation for this type support? Thank you!

[mosabua]

Docs need some clarification and refinement. Great start and thanks for not ignoring the docs @adamjshook

[mosabua]

How about

Enable support for encoding Protobuf any types to JSON by setting to the property to true, defaults to false.

[mosabua]

same length as title

[mosabua]

This reads weird .. how about

Message types with an Any field contain an arbitrary ...

[adamjshook]

@mosabua I've made updates to the documentation, please give it another review and let me know of any changes. Thank you!

[mosabua]

One last nit, but essentially the docs are good to go.

[mosabua]

Suggested change

	The corresponding Trino column will be named ``any_message`` of type ``JSON``
	The corresponding Trino column is named ``any_message`` of type ``JSON``

[adamjshook]

@hashhar I've rebased against master to pick up the changes from #17858.

[hashhar]

LGTM % some docs comments

[hashhar]

Suggested change

	``kafka.protobuf-any-support-enabled`` Enable support for encoding Protobuf any types to JSON by setting to the property to ``true``,
	``kafka.protobuf-any-support-enabled`` Enable support for encoding Protobuf ``any`` types to ``JSON`` by setting to the property to ``true``,

[hashhar]

are schemes other than file://, http:// or https:// supported? If not let's word this more explicitly to say exactly what schemes are supported.

[adamjshook]

No, I've changed the docs to be more clear.

[hashhar]

Rebased to resolve conflicts. Will merge after CI.