Is your feature request related to a problem? Please describe.
Use multiple online store backends for different teams or use cases within the same Feast deployment. Currently, Feast only supports a single online store per project, which limits flexibility and makes it difficult to manage multi-tenant or hybrid storage scenarios.

Describe the solution you'd like
To support a Hybrid Online Store that can dynamically route online feature data to different backend stores based on tags (such as "team" or "tribe") on FeatureViews. This would allow configuring multiple online stores in the same project and routing requests to the appropriate backend automatically.
.

Describe alternatives you've considered
Running multiple separate Feast projects, each with its own online store backend. This increases operational overhead and complicates management.
Manually implementing routing logic outside of Feast, which is error-prone and not scalable.

Additional context
The Hybrid Online Store would inspect a tag (e.g., "team") on each FeatureView and use it to select the correct backend from the configured online stores. This enables multi-tenant, flexible deployments and centralizes management.
See the https://github.com/feast-dev/feast/blob/master/docs/reference/online-stores/hybrid.md documentation for more details and configuration examples.