Forward expected `HederaFunctionality` from gRPC endpoint to `IngestWorkflow`

Structurally, every gRPC service endpoint has the "signature" `Transaction -> TransactionResponse`.

But we would like to,
- [ ] Restrict the allowed transactions for each service endpoint to just the function implied by the gRPC endpoint.
- [ ] Add configuration to support registering just a subset of service endpoints.

Start by tracing how each gRPC service endpoint forwards a Transaction to IngestWorkflow and where the expected HederaFunctionality is available. Done means endpoints restrict accepted transactions to their implied function and configuration can register only a selected subset of service endpoints.

Written by the indexing model from the issue text.