Support UDS listen address for tokio-console

[teskje]

This PR fixes local tokio-console support, which was broken in ac1028d because tokio-console does not support Unix domain sockets (yet, see: tokio-rs/console#388).

The fix involves adding that support by switching to @benesch's fork of concole-subscriber and using the mz_ore::netio::SocketAddr type for the tokio-console listen address.

It is now also required to use the forked version of the tokio-console CLI client. The developer docs are updated to reflect this.

Motivation

• This PR fixes a previously unreported bug.

Running environmentd with tokio-console support enabled is broken:

environmentd: 2022-12-09T12:23:53.131943Z  INFO mz_orchestrator_process: launching compute-cluster-s1-replica-2-0 via --controller-listen-addr=/var/folders/30/xdglsm2j3tz1rn1n7yygtm7c0000gn/T/3936d1d75b734cbabb3d0678b275c3deafe82812 --internal-http-listen-addr=/var/folders/30/xdglsm2j3tz1rn1n7yygtm7c0000gn/T/c489d7731630ec1fa5fb8ddba4c0da9dd9c9eafb --opentelemetry-resource=instance_id=s1 --opentelemetry-resource=replica_id=2 --log-filter=info --log-format=text --log-prefix=compute-cluster-s1-replica-2 --tokio-console-listen-addr=/var/folders/30/xdglsm2j3tz1rn1n7yygtm7c0000gn/T/1209e7e52cdc107ee25ca4998196aa23922fb9e4 --tokio-console-publish-interval=1000000 us --tokio-console-retention=3600000000 us --pid-file-location=/private/var/folders/30/xdglsm2j3tz1rn1n7yygtm7c0000gn/T/environmentd-local-az1-2ba6f456-fae2-4c9b-a8df-8f398ee4cb82-0/compute-cluster-s1-replica-2/0.pid --secrets-reader=process --secrets-reader-process-dir=/Users/jan/devel/materialize/mzdata/secrets...
error: Invalid value "/var/folders/30/xdglsm2j3tz1rn1n7yygtm7c0000gn/T/d8309b97c7d54152fe0a4ded500c397714d4b559" for '--tokio-console-listen-addr <TOKIO_CONSOLE_LISTEN_ADDR>': invalid socket address syntax

For more information try --help
environmentd: 2022-12-09T12:23:53.149669Z ERROR mz_orchestrator_process: compute-cluster-s2-replica-3-0 exited: ExitStatus(unix_wait_status(512)); relaunching in 5s

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered.

• This PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way) and therefore is tagged with a T-proto label.

• This PR includes the following user-facing behavior changes:

[benesch]

Thanks, @teskje! LGTM. I pushed up a slight modification to move the Git reference to a MaterializeInc fork, since the uds branch is associated with a PR that's still undergoing review, and I might force push at it. We can keep the MaterializeInc fork stable though.