Analytics: Handle JSON stringify errors

[tyxla]

Proposed Changes

Handle errors in JSON stringify when debugging analytics.

Why are these changes being made?

Just handling potential errors.

See #98326 and #98464

Testing Instructions

Same as #98326.

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

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

name                 parsed_size           gzip_size
entry-subscriptions        +40 B  (+0.0%)      +26 B  (+0.0%)
entry-stepper              +40 B  (+0.0%)      +26 B  (+0.0%)
entry-main                 +40 B  (+0.0%)      +26 B  (+0.0%)
entry-login                +40 B  (+0.0%)      +26 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.

[matticbot]

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

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

• blaze-dashboard
• notifications
• odyssey-stats
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/analytics-handle-stringify-errors on your sandbox.