feat: add prism connector audit logs

[VenuMadhav2541]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Adds Prism connector event logs to the existing connector audit timeline for payment, refund, dispute, and payout audit screens.

This PR keeps Prism events under the existing connector section and updates the connector event display name logic to use the destination field:

• UCS connector audit events for authentication flows are shown as Internal Authentication.
• Prism connector audit events for authentication flows are shown as Authentication.
• Non-authentication connector flows continue to use the existing API name mapping.

Fixes #5130

Motivation and Context

The backend now exposes Prism connector event audit rows through the analytics API. The dashboard needs to fetch those rows and render them with the existing connector audit events so users can see the complete connector timeline for UCS and Prism based payment flows.

How did you test it?

• Before:

- After:

Where to test it?

• INTEG
• SANDBOX
• PROD

Backend Dependency

• Yes
• No

Backend PR URL: juspay/hyperswitch#13177

Feature Flag

• New feature flag added
• Existing feature flag updated
• No feature flag changes

Feature flag name(s):

Checklist

• I ran npm run re:build
• I reviewed submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
playwright-tests/support/commands.ts	0% smaller
src/APIUtils/APIUtils.res	Unsupported file format
src/APIUtils/APIUtilsTypes.res	Unsupported file format
src/screens/Analytics/Logs/DisputeLogs/DisputeLogs.res	Unsupported file format
src/screens/Analytics/Logs/LogUtils/LogTypes.res	Unsupported file format
src/screens/Analytics/Logs/LogUtils/LogUtils.res	Unsupported file format
src/screens/Analytics/Logs/PaymentLogs/PaymentLogs.res	Unsupported file format
src/screens/Analytics/Logs/RefundLogs/RefundLogs.res	Unsupported file format
src/screens/Payouts/PayoutLogs.res	Unsupported file format

[XyneSpaces]

🚨 [blocking] getConnectorResponse in LogUtils.res falls back from masked_response to the raw response field when the masked value is empty.

Previously connector logs only rendered masked_response, which is the sanitized output. Showing the raw response when masking is absent exposes the full connector payload in the dashboard and breaches the masking contract. This affects getResponseObject, setDefaultValue, and the CONNECTOR log type rendering.

Treat an empty masked_response as missing data rather than falling back to the unsanitized response field, or ensure the log source always populates masked_response before this code reaches production.

let getConnectorResponse = dict => {
  dict->getString("masked_response", "")
}

[XyneSpaces]

[should-fix] getConnectorResponse falls back to the raw response field whenever masked_response is empty, which can leak unmasked PCI/PII in connector audit logs.

In src/screens/Analytics/Logs/LogUtils/LogUtils.res:

let getConnectorResponse = dict => {
  let maskedResponse = dict->getString("masked_response", "")
  maskedResponse->isNonEmptyString ? maskedResponse : dict->getString("response", "")
}

If the backend omits masked_response for any connector log whose response contains sensitive data, the audit-log UI will render it unredacted. The previous code only rendered masked_response for CONNECTOR logs, so this fallback relaxes the masking boundary.

Suggestion: only fall back to response when you have a positive signal that it is safe (for example, a is_masked flag or a dedicated non-sensitive display_response field), otherwise keep the previous behavior of returning an empty/default value when masking metadata is missing.