Tailored Flows: Remove /setup/blog flow

[mmtr]

Part of https://github.com/Automattic/dotcom-forge/issues/9333

Proposed Changes

Removes the code associated to the /setup/blog tailored blow since we no longer use it.

Why are these changes being made?

To clean up unused code.

Testing Instructions

• Go to /setup/blog
• Make sure it still redirects to /start

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

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-122646&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 (~170 bytes removed 📉 [gzipped])

name                   parsed_size           gzip_size
entry-stepper               -467 B  (-0.0%)     -170 B  (-0.0%)
entry-subscriptions         -385 B  (-0.0%)     -154 B  (-0.0%)
entry-main                  -385 B  (-0.0%)     -154 B  (-0.0%)
entry-login                 -385 B  (-0.0%)     -154 B  (-0.0%)
entry-domains-landing       -385 B  (-0.1%)     -154 B  (-0.1%)
entry-browsehappy           -385 B  (-0.2%)     -154 B  (-0.3%)

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

Sections (~882 bytes removed 📉 [gzipped])

name                  parsed_size             gzip_size
blog                      -1723 B  (deleted)     -873 B  (deleted)
update-design-flow          -12 B    (-0.0%)       -2 B    (-0.0%)
link-in-bio-tld-flow        -12 B    (-0.0%)       -5 B    (-0.0%)
copy-site-flow              -12 B    (-0.0%)       -2 B    (-0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~7 bytes removed 📉 [gzipped])

name                             parsed_size           gzip_size
async-load-signup-steps-domains        -12 B  (-0.0%)       -7 B  (-0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

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.

[xavier-lc]

Works as described

[rcrdortiz]

Created a PR to handle redirections outside of the stepper framework here:

• Redirect Flows: We now redirect without using the Stepper framework #95574

[matticbot]

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

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

• blaze-dashboard
• command-palette-wp-admin
• help-center
• notifications
• odyssey-stats
• whats-new

To test WordPress.com changes, run install-plugin.sh $pluginSlug remove/blog-tailored-flow on your sandbox.