Support Multi Shard Clickhouse DB for Langfuse

[RahulMR42]

Describe the feature or potential improvement

What we think / aware that - Langfuse itself does not usually provide a native “shard routing” layer where it splits tenant/workload across multiple independent backends automatically. If you need that, it’s typically done by deploying multiple Langfuse stacks (e.g., per org/region/environment) and routing traffic externally. We would like to know is there a roadmap to support multi shard auto scalable Clickhouse DB support for Langfuse

Additional information

No response

[Steffen911]

This is a duplicate of https://github.com/orgs/langfuse/discussions/5021.