feat(tsys_transit): track Hyperswitch UCS integration

[awasthi21]

Summary

Track the Hyperswitch-side TSYS TransIT integration work for routing tsys_transit through Unified Connector Service (UCS) and supporting certification flows.

Scope

• Add Hyperswitch connector enum/config wiring for tsys_transit.
• Route TSYS TransIT payment flows through UCS using ucs_only_connectors.
• Forward required payment data from HS into UCS for MOTO, auth, void, capture, refund, recurring/installment, and Level II/III certification flows.
• Preserve TSYS commercial-card and transaction evidence requirements without committing local credentials or raw certification artifacts.
• Keep HS-side connector auth shape compatible with UCS TsysTransit auth conversion.

Linked PR

• feat(tsys_xml): route connector through UCS #12545

Validation Notes

Local smoke validation completed against running local HS + local UCS + TSYS stage gateway:

• HS v1 auth endpoint: POST /payments
• HS v1 void endpoint: POST /payments/{payment_id}/cancel
• UCS gRPC: PaymentService/Authorize and PaymentService/Void
• TSYS gateway endpoint: https://stagegw.transnox.com/servlets/TransNox_API_Server
• Latest smoke result: manual auth returned requires_capture, void returned cancelled, TSYS returned A0000 for both.

Follow-ups / Risks

• Ensure tsys_transit uses the same connector TOML/config path pattern as other UCS-only connectors instead of returning None from connector config lookup.
• Return/refund reversal needs a separate HS/UCS route and should not be mixed into this integration PR.
• Do not commit API keys, MCA IDs, raw PAN/CVV, TSYS credentials, or local certification evidence.

[awasthi21]

Linked Hyperswitch PR: #12545

This issue tracks the HS-side TSYS Transit/UCS integration and the connector config/auth exposure follow-up.