Performance Profiler: Add chatId to track events for LLM survey

[epeicher]

Resolves https://github.com/Automattic/dotcom-forge/issues/9873

Proposed Changes

• Adds url, hash and chatId to calypso_performance_profiler_llm_survey_click track event

Please note: I didn't add the message_id to the track event because with the chat_id, the messages are very easy to identify (currently there is only one message), and I don't think it is necessary. But if required, it would be straightforward to add it.

Why are these changes being made?

• It will allow to identify chats that are rated to further analyse the responses

Testing Instructions

• Apply this patch and run a test using the speed test tool, or navigate to an existing report, e.g. /speed-test-tool?hash=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpZCI6NzA3MX0.m3-63iGZmpJOpOfkZ4ww184EoKd8P3UHzTYwv1VLQUo&url=https%3A%2F%2Fwordpress.com%2F&tab=mobile
• Open the developer tools, select the Network tab and filter the requests for t.gif, additionally, use the Tracks Vigilante or any other tool to inspect the Tracks events.
• Expand an insight and wait for the result to appear
• Click on the Survey, either good or bad
• Check that the calypso_performance_profiler_llm_survey_click track event is sent and it contains the proper url, hash and chatId

Pre-merge Checklist

• [ ] Has the general commit checklist been followed? (PCYsg-hS-p2)
• [ ] Have you written new tests for your changes?
• [ ] Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• [ ] Have you checked for TypeScript, React or other console errors?
• [ ] Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• [ ] Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• [ ] For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions[bot]]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-124939

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-124939&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-124939&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~49 bytes added 📈 [gzipped])

``` name parsed_size gzip_size site-performance +127 B (+0.0%) +49 B (+0.0%) performance-profiler +127 B (+0.0%) +49 B (+0.0%) ``` Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

**Parsed Size:** Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. **Gzip Size:** Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/perf-profiler-llm-click-track-event on your sandbox.