feat: session-scoped correlation ID on feedback analytics events

[MaVictor]

Description

Mint one correlation ID per studio-mcp process, each ADE/IDE connection gets a fresh process, and stamp it on every snyk_send_feedback analytics event via NewAnalyticsEventParam, so events emitted by the same session can be joined downstream instead of each call minting its own random ID.

Checklist

• Tests added and all succeed
• Regenerated mocks, etc. (make generate)
• Linted (make lint-fix)
• README.md updated, if user-facing
• License file updated, if new 3rd-party dependency is introduced

---

Note

Low Risk
Analytics-only metadata change with backward-compatible empty correlation ID; behavior is covered by unit and handler tests with no changes to auth or tool logic.

Overview
snyk_send_feedback analytics can now be joined per MCP session instead of each tool call getting its own interaction ID.

The MCP binding mints one UUID when Start() runs (once per studio-mcp process) and passes it into NewAnalyticsEventParam, which sets InteractionUUID so PayloadForAnalyticsEventParam emits a stable urn:snyk:interaction:<id> on every feedback event in that session. snyk_send_feedback is wired to use m.correlationID; an empty correlation ID still defers to the existing per-event UUID minting for other callers.

Tests cover the analytics helpers, idempotent minting on McpLLMBinding, and an end-to-end handler test that asserts two feedback calls share the same interaction URN in the analytics payload.

^{Reviewed by Cursor Bugbot for commit 787ae29. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[ifeanyiecheruo]

Changes look good