feat: Enhance customization of Trino connections when using Trino-based Offline Stores

[boliri]

What this PR does / why we need it:

Right now, the Trino Offline Store implementation lacks support for authentication. Taking a look at the code it seems like it is supported via the TRINO_AUTH environment variable; however, environment variables can only hold string values. The issue here is that TRINO_AUTH is passed to trino.dbapi.connect as is (i.e. a string), but it must be a trino.Authentication instance. So in practice, there's no way to make authentication work.

Aside from that, the current implementation supports customizing Trino connections via feature_store.yaml file, or via environment variables as hinted above. Particularly, the set of supported parameters on both sides is as follows:

feature_store.yaml

• host
• port
• catalog

Environment variables

• TRINO_HOST (mirror of feature_store.yaml's host parameter)
• TRINO_PORT (mirror of feature_store.yaml's port parameter)
• TRINO_USER
• TRINO_CATALOG (mirror of feature_store.yaml's catalog parameter)
• TRINO_HTTP_SCHEME
• TRINO_SOURCE
• TRINO_EXTRA_CREDENTIAL
• TRINO_AUTH (supported but not usable, as explained above)

These configurations should be doable through the feature_store.yaml file to be consistent with the set of parameters already supported. Hence this PR.

A word of warning on compatibility

If you are using some of the environment variables above to customize Trino connections, you must update your feature_store.yaml file to make sure your setup doesn't break.

An example on how to incorporate those environment variables into your feature_store.yaml:

offline_store:
    type: feast_trino.trino.TrinoOfflineStore
    host: $TRINO_HOST
    port: $TRINO_PORT
    catalog: $TRINO_CATALOG
    connector:
        type: memory
    user: $TRINO_USER
    source: $TRINO_SOURCE
    http-scheme: $TRINO_HTTP_SCHEME
    x-trino-extra-credential-header: $TRINO_EXTRA_CREDENTIAL

Which issue(s) this PR fixes:

• Unify Trino connections' configuration in a single point (feature_store.yaml) to ease customization.
• Add an extra configuration (ssl-verify) to specify whether Trino SSL certificates should be validated on feast's side or not. This parameter is the equivalent to the verify flag in popular Python HTTP libs like requests.
• Ensure that the TrinoOfflineStore class satisfies the signature of abstract methods included in the OfflineStore abstract class.
• Add support for multiple authentication mechanisms:
  • Kerberos
  • Basic Auth
  • JWT
  • OAuth2
  • Certificate
• Update Trino Offline Store's docs to provide examples on how to customize these connections.

Fixes #

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: boliri
To complete the pull request process, please assign chhabrakadabra after the PR has been reviewed.
You can assign the PR to them by writing /assign @chhabrakadabra in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment