fix(connectivity): dial ledger v3 gRPC by Service name, not TLS SNI

[Dav-14]

ledgerAddress was built from backend.TLS.ServerName, the SNI/certificate FQDN
(ledger-..svc.cluster.local). On clusters whose DNS domain is not
cluster.local that FQDN need not resolve, so connectivity-core could not reach
the ledger. Build the dial address from backend.Name — the Service name, which
resolves in the stack namespace on any DNS domain — and keep TLS.ServerName as
the SNI on spec.ledgerTLS for certificate verification, mirroring how the gateway
upstream dials its backend.

Addresses NumaryBot finding 52f0f4a930fa3d33.

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c7d164a5-79c2-4e94-a341-3cb7b93d210a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Dav-14]

Superseded by #492, which includes this fix and verifies the Service dial address while preserving the TLS SNI.