Tokio-console subscriber configuration

[AhmedSoliman]

Adds a configuration key in common to configure tokio-console subscriber bind address (support unix-sockets btw). Moreover, this lets tokio-console subscriber bind on all interfaces by default to make it easy to introspect restate-server running in docker containers.

Stack created with Sapling. Best reviewed with ReviewStack.

• [TaskCenter] Stage 1 of task-center clean-up #2330
• Fix schemar's type in rocksdb config #2329
• -> Tokio-console subscriber configuration #2323

[github-actions]

Test Results

  7 files  ±0    7 suites  ±0   4m 22s ⏱️ +2s
 47 tests ±0   46 ✅ ±0  1 💤 ±0  0 ❌ ±0 
182 runs  ±0  179 ✅ ±0  3 💤 ±0  0 ❌ ±0 

Results for commit b847c55. ± Comparison against base commit b82d591.

♻️ This comment has been updated with latest results.

[tillrohrmann]

Thanks for making the bind port of the tokio console subscriber configurable @AhmedSoliman. The changes look good to me. A few tests seem to fail now because tokio console cannot bind to the specified port. Probably we need to assign a random port or a random unix domain socket here

restate/crates/local-cluster-runner/src/node/mod.rs

Lines 61 to 68 in 2ec5491

	pub fn with_random_ports(self) {
	self.base_config.admin.bind_address =
	random_socket_address().expect("to find a random port for the admin server");
	self.base_config.admin.query_engine.pgsql_bind_address =
	random_socket_address().expect("to find a random port for the pgsql server");
	self.base_config.ingress.bind_address =
	random_socket_address().expect("to find a random port for the ingress server");
	}

.

[muhamadazmy]

Looks awesome! Thank you for this PR