Allow injecting authentication components for ThriftMetastore

[phd3]

Description

We've a requirement for using an external service to authenticate to HMS as Trino, and also fetch HMS delegation tokens for the end-user. So proposing this change to make these components to be provided by an external module. ( Using optional binder to avoid having to make ThriftMetastoreAuthenticationType enum a string)

The PR contains following major changes:

• Rename the Thrift metastore client factories to distinguish them better given what the interface exposes

Interface old name	Signature	Return Type	New name
ThriftMetastoreFactory (highest level)	createMetastore(Optional<ConnectorIdentity> identity)	ThriftMetastore	ThriftMetastoreFactory (unchanged)
TokenDelegationThriftMetastoreFactory	createMetastoreClient(Optional<ConnectorIdentity> identity)	ThriftMetastoreClient	IdentityAwareMetastoreClientFactory
MetastoreLocator	createMetastoreClient(Optional<String> token)	ThriftMetastoreClient	TokenAwareMetastoreClientFactory
ThriftMetastoreClientFactory (lowest level)	create(HostAndPort address, Optional<String> delegationToken)	ThriftMetastoreClient	ThriftMetastoreClientFactory (unchanged)

• Narrow down usage of ThriftMetastoreAuthenticationType to make auth decision. (Also makes TokenDelegationThriftMetastoreFactory aka IdentityAwareMetastoreClientFactory an interface)

• Allow binding your own thrift authentication module

Related issues, pull requests, and links

Documentation

( ) 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

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

# Section
* Fix some things. ({issue}`issuenumber`)

[phd3]

@dain @electrum can you please take a look?

[phd3]

Rebased with some modifications to align with the recent refactoring. some more details in PR description. @dain @losipiuk does this approach look reasonable?

[phd3]

cc @electrum

[dain]

Couple of minor comments, but otherwise looks good