Design Picker: Remove Trending for your goals section

[taipeicoder]

Related to #97718

Proposed Changes

This PR removes the "Trending for your goals" section since it didn't quite fit with the Design Picker due to it being related to goals instead of category filters.

Why are these changes being made?

#97718 (comment)

Testing Instructions

• Head to the Design Picker.
• Smoke-test to ensure it works as intended.

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 UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• 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-129426

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-129426&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 remove/design-picker-recommended-themes on your sandbox.

[matticbot]

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

Sections (~75 bytes removed 📉 [gzipped])

name                  parsed_size           gzip_size
link-in-bio-tld-flow        -72 B  (-0.0%)      -32 B  (-0.0%)
update-design-flow          -40 B  (-0.0%)      -21 B  (-0.0%)
themes                      -40 B  (-0.0%)      -21 B  (-0.0%)
signup                      -40 B  (-0.0%)      -21 B  (-0.0%)
marketplace                 -40 B  (-0.0%)      -22 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 (~20 bytes removed 📉 [gzipped])

name                      parsed_size           gzip_size
async-load-design-blocks        -40 B  (-0.0%)      -20 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.

[madhusudhand]

Verified the changes. LGTM! 🚢

[richtabor]

I suggest "Best theme matches" rather than "Best matching themes".

It's more natural, conversational, and direct, aligning with user expectations when scanning for relevant options.

[taipeicoder]

I suggest "Best theme matches" rather than "Best matching themes".

It's more natural, conversational, and direct, aligning with user expectations when scanning for relevant options.

Sounds good, updated to "Best theme matches" cc: @fditrapani

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/17139340

Some locales (Hebrew, Japanese) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

Thank you @taipeicoder for including a screenshot in the description! This is really helpful for our translators.