Add properties to Funnel

[lmuntaner]

Motivation

Properties need to be set in all the events in order to be able filter Funnels by them.

For example, to check the Funnel of NNS Dapp logins, we need to always set the origin of NNS Dapp in all the events triggered in that Funnel.

Changes

This pull request includes enhancements to the Funnel class and its associated tests to support the inclusion of properties in analytics events. The changes ensure that properties can be passed during initialization and triggering of events, and that these properties are correctly merged and tracked.

Enhancements to Funnel class:

• src/frontend/src/utils/analytics/Funnel.ts: Added support for properties in the init and trigger methods, and modified the close method to include these properties when tracking the duration.

Enhancements to Funnel tests:

• src/frontend/src/utils/analytics/Funnel.test.ts: Added new test cases to verify that properties are correctly passed and merged in the init and trigger methods, and that the close method tracks the duration with these properties.

---

🟡 Some screens were changed

[Copilot]

Pull Request Overview

This PR enhances the Funnel class to support passing properties for analytics events, allowing events to include additional context data such as the userId and source.

• Modified the Funnel class to accept and forward optional properties in the init and trigger methods, and to include these properties in the close event.
• Updated the Funnel tests to verify that events are correctly sent with or without properties, and that property merging works as expected.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/frontend/src/utils/analytics/Funnel.ts	Enhanced the Funnel class to support optional properties with analytics events by adding parameters and merging properties where appropriate.
src/frontend/src/utils/analytics/Funnel.test.ts	Extended tests to cover the new behavior of passing and merging properties in init, trigger, and close methods.

Comments suppressed due to low confidence (1)

src/frontend/src/utils/analytics/Funnel.ts:55

• [nitpick] Consider resetting the stored properties (this.#properties) to undefined at the end of the close() method after triggering the final analytics event to ensure the funnel state is fully reset and to avoid potential unintended reuse of stale properties.

this.#startTimestamp = undefined;