feat(hubtype-analytics): add webview params to event WebviewActionTriggered #BLT-2466

[Iru89]

Description

Add optional webview parameters to the WebviewActionTriggered analytics event so Flow Builder webview actions can report the parameters used to open the webview.

Context

Webview trigger parameters are useful for understanding the context in which a webview was opened and for correlating analytics with the data passed to the webview. The field is optional to preserve compatibility with existing webview events that do not provide parameters.

Approach taken / Explain the design

• Add webviewParams as an optional Record<string, string> to the shared EventWebviewActionTriggered model.
• Pass FlowWebview.webviewParams to the analytics tracking event.
• Map the property to the snake_case webview_params field in HtEventWebviewActionTriggered.
• Keep the property optional so existing event producers and consumers remain compatible.

To document / Usage example

When a webview is triggered with parameters:

{
  webviewTargetId: 'booking-webview',
  webviewName: 'BOOKING',
  webviewParams: {
    bookingId: '12345',
    source: 'confirmation',
  },
}

The analytics event includes:

{
  webview_target_id: 'booking-webview',
  webview_name: 'BOOKING',
  webview_params: {
    bookingId: '12345',
    source: 'confirmation',
  },
}

Testing

The pull request...

• has unit tests covering the propagation of webview parameters from the event model to the analytics event.
• doesn't have integration tests because this change is limited to event data mapping and is covered by the unit test suite.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

[github-actions]

Test Results

46 tests  ±0   46 ✅ ±0   1m 33s ⏱️ -1s
 6 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 6e82944. ± Comparison against base commit 893b107.