control plane actor in crash loop: list_shards is not implemented for PostgreSQL metastore

[jeromegn]

Describe the bug

thread 'tokio-runtime-worker' panicked at 'not implemented: `list_shards` is not implemented for PostgreSQL metastore', quickwit-metastore/src/metastore/postgresql_metastore.rs:1310:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_fmt
             at /rustc/d5c2e9c342b358556da91d61ed4133f6f50fc0c3/library/core/src/panicking.rs:67:14
   2: <quickwit_metastore::metastore::postgresql_metastore::PostgresqlMetastore as quickwit_proto::metastore::MetastoreService>::list_shards::{{closure}}
   3: quickwit_proto::metastore::<impl tower_service::Service<quickwit_proto::metastore::ListShardsRequest> for alloc::boxed::Box<dyn quickwit_proto::metastore::MetastoreService>>::call::{{closure}}
   4: <quickwit_common::tower::metrics::ResponseFuture<_,F> as core::future::future::Future>::poll
   5: <quickwit_proto::metastore::MetastoreServiceTowerBlock as quickwit_proto::metastore::MetastoreService>::list_shards::{{closure}}
   6: <quickwit_proto::metastore::MetastoreServiceClient as quickwit_proto::metastore::MetastoreService>::list_shards::{{closure}}
   7: quickwit_proto::metastore::<impl tower_service::Service<quickwit_proto::metastore::ListShardsRequest> for alloc::boxed::Box<dyn quickwit_proto::metastore::MetastoreService>>::call::{{closure}}
   8: <core::pin::Pin<P> as core::future::future::Future>::poll
   9: <quickwit_proto::metastore::MetastoreServiceTowerBlock as quickwit_proto::metastore::MetastoreService>::list_shards::{{closure}}
  10: <quickwit_proto::metastore::MetastoreServiceClient as quickwit_proto::metastore::MetastoreService>::list_shards::{{closure}}
  11: <quickwit_control_plane::control_plane::ControlPlane as quickwit_actors::actor::Actor>::initialize::{{closure}}
  12: quickwit_actors::spawn_builder::SpawnBuilder<A>::spawn::{{closure}}
  13: tokio::runtime::task::core::Core<T,S>::poll
  14: tokio::runtime::task::harness::Harness<T,S>::poll
  15: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
  16: tokio::runtime::scheduler::multi_thread::worker::Context::run
  17: tokio::runtime::context::scoped::Scoped<T>::set
  18: tokio::runtime::scheduler::multi_thread::worker::run
  19: tokio::runtime::task::core::Core<T,S>::poll
  20: tokio::runtime::task::harness::Harness<T,S>::poll
  21: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Steps to reproduce (if applicable)

I think just using the postgres metastore triggers this.

Configuration:

I'm using 8d00ad1