Remove forced sites fallback

[lsl]

Related to # https://github.com/Automattic/dotcom-forge/issues/8070

Proposed Changes

• Removes forced /sites fallback from sidebar links allowing the global sidebar to determine the back link location

Testing Instructions

• Click around global nav ensure back links make sense

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-113159&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 update/reader-back on your sandbox.

[matticbot]

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

Sections (~11 bytes removed 📉 [gzipped])

name                             parsed_size           gzip_size
plugins                                -22 B  (-0.0%)      -11 B  (-0.0%)
jetpack-cloud-plugin-management        -22 B  (-0.0%)      -11 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.

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.

[lsl]

Pushed to share the offending code seam, doesn't actually fix the problem, see discussion here