Use the same grpc:// client for both Storage Node and re_grpc_server

[emilk]

As a user, I want to write rerun grpc://some-ip and not care if what I'm talking to is re_grpc_server or the storage node.

Right now SN and re_grpc_server has no overlap in functionality, but eventually they will (e.g. both should be able to list a catalogue of recordings in it).

This will fix the temp:// schema thing added in

• Implement gRPC log stream #8730

We could use a REST-like url parsing scheme, e.g. grpc://ip/recording/recording-id vs grpc://ip/events, and have that decide which rpc endpoint is hit.

We should probably unify the two gRPC clients regardless, since eventually there will be overlap in functionality between the two servers.