Stepper: Log event on page load

[renancarvalho]

Related to #94717
Fixes #94717

Proposed Changes

• Make sure it calls recordSignupStart on page load, currently there's an issue that it is not called upon page refresh.
• Add useEffect hook together with initialState variable to handle page load

Why are these changes being made?

• Fix Stepper: calypso_signup_start not being triggered on refresh #94717

Testing Instructions

• Use live link and navigate to /setup/onboarding
• On domains or plans step, make sure the calypso_signup_start is triggered only once upon page refresh.
• Navigate between steps and refresh the page, it should log only once.
• Use /start/onboarding as a reference

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)?

[matticbot]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[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 fix/domains_tracking_mount on your sandbox.

[matticbot]

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

App Entrypoints (~28 bytes added 📈 [gzipped])

name           parsed_size           gzip_size
entry-stepper        +98 B  (+0.0%)      +28 B  (+0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

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.

[chriskmnds]

On domains or plans step, make sure the calypso_signup_start is triggered only once upon page refresh.
Navigate between steps and refresh the page, it should log only once.

This is the basis that I am basically questioning below. Please feel free to object/question the direction.

I have a separate PR that makes this hook record the event unconditionally and also handles not being recorded on refresh. See #94743

Let's please hold off proceeding here until we review #94743, as that may be the direction to go

[chriskmnds]

This leads to the same situation we are trying to resolve in discussion #94175 (comment)

We shouldn't ignore any additional/extra props. If the event gets recorded multiple times because of it, then so be it. Analytics can pick the first. This is my understanding from it, and how we can proceed.