Use origin on login and registration funnel

[lmuntaner]

Motivation

Enable filtering the funnel per application.

Changes

This pull request includes changes to improve the initialization of analytics funnels and the authentication protocol in the frontend code. The most important changes include initializing both loginFunnel and registrationFunnel with the request origin, and ensuring funnels are initialized in the manage flow (when user doesn't come from a dapp).

Improvements to analytics funnels:

• src/frontend/src/flows/authorize/postMessageInterface.ts: Initialized both loginFunnel and registrationFunnel with the request origin in the authenticationProtocol function.
• src/frontend/src/index.ts: Initialized both loginFunnel and registrationFunnel in the default flow without origin.
• src/frontend/src/index.ts: Removed redundant registrationFunnel.init() call in the #authorize hash routing.

Tests

Tested locally that events are triggered as expected.

---

🟡 Some screens were changed

[Copilot]

Pull Request Overview

This PR enhances analytics funnel initialization by incorporating the request origin into both login and registration funnels for the authentication protocol and adjusting their initialization in the manage flow.

• Updated authenticationProtocol to pass the origin to both funnels.
• Adjusted funnel initialization in the default (manage) flow to initialize without origin.

Reviewed Changes

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

File	Description
src/frontend/src/index.ts	Added loginFunnel import and updated funnel initialization order.
src/frontend/src/flows/authorize/postMessageInterface.ts	Updated funnel initialization to pass the request origin.