Access and configure underlying gRPC connection for core components

Is your feature request related to a problem? Please describe.
Core Temporal components connect to each other over a gRPC connection configured within the Temporal server codebase. An individual instance of Temporal Server does not have access to and cannot configure the underlying connection.

Without the ability to configure/intercept that connection when a Temporal server component is started, we cannot add things like custom tracing or grpc.WithPerRPCCredentials.

These are necessary so we can properly identify services when they reach out Temporal frontend

Describe the solution you'd like
Temporal server components would expose access to their underlying gRPC connection during initialization. A user can set custom dial options and/or interceptors on the underlying connection.

Describe alternatives you've considered
As far as I've been able to tell, no implementation exists in Temporal Server for this level of control.

The issue names no files, tests, or initialization entry points. Start by locating how Temporal server core components create their gRPC connections, then determine the configuration or interception surface needed during component startup. Done means users can supply custom dial options or interceptors, including tracing and per-RPC credentials, with coverage for the supported behavior.