A materialization of this kind is purely descriptive, and cannot be directly started. It is used to convey the intent to expose a set of bindings through Dekaf, which will look it up to determine things like binding names and field selection/projections.

…very journals, but they _should_ get ops stats+logs collections

…::Dekaf`

…rticular dekaf binding

Largely retain the same functionality as `flowctl::Client`, just in a new home so that it can be shared without introducing inconvenient dependencies

…, and re-use Postgrest connection pool instead of creating a new one on each call to `pg_client()`

`flowctl` needs these credentials exposed in order to store them in `flowctl::Config` + on disk for the next flowctl invocation

… API key

…seconds to respond

…_gazette_client()`

gRPC connections seem to lose stability after a while, this temporarily fixes that