Boost: Add "load default strings" to excludes in concatenate UI

[dilirity]

Proposed changes:

• Add a button, similar to cornerstone pages, that loads default exclude values for concatenate JS and CSS;
• Clean up CSS in minify component.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

n/a

Does this pull request change what data or activity we track or use?

no

Testing instructions:

• Setup Boost;
• Make sure concatenate JS/CSS UI is behaving as expected.

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

---

Boost plugin:

• Next scheduled release: none scheduled.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[donnchawp]

Some minor things, but looks good otherwise.

[donnchawp]

I'd much rather we didn't use "strings" here or in the sub header. Yes, they literally are strings, but they're the handles used to register JS and CSS files. Strings describes what those pixels on the screen are, not what they do or represent
.
Maybe use "scripts" instead? "JS Scripts" "CSS Scripts" ?

I'm not sure. Could be a job for another PR.

[haqadn]

I agree. The values aren't just strings. They are handles. I'd suggest calling them "default handles" as well.

[dilirity]

I don't mind calling them handles, I'm worried that a lot of users have no idea what that means. We're mentioning strings everywhere.

[dilirity]

Changed in 34fde9b.

We should probably change the labels as well.

[donnchawp]

I should have looked more carefully at the modules.

In the JS module:

1. "Scripts" is used to describe the files loaded.
2. The toggle says, "Exclude JS Strings".
3. The sub header says, "Exclude JS Strings".

In the CSS module:

1. "Styles" is used to describe the files loaded.
2. The toggle says, "Exclude CSS Strings".
3. The sub header says, "Exclude CSS Strings".

This patch adds a button saying, "Load default handles".

Would it be better to use "scripts" in the JS module, and "styles" in the CSS module? This is what it might look like:

[dilirity]

What if we drop "Scripts/Styles" from the label and just say "Exclude JS" or "Exclude CSS".

Then we could update the description to say "handles" and maybe add a link to a support article that mentions how to identify those? Then the button will be "Load default handles".

[donnchawp]

That makes sense when I say "JS scripts" out loud, as in "JavaScript scripts". It's a bit cumbersome.
I'd go one step further and change that last string to "Load Defaults" too. No need to confuse the user with new jargon.

[dilirity]

I'd go one step further and change that last string to "Load Defaults" too.

Funny you should say that. I intentionally added what is being loaded (hence the strings part), since @haqadn pointed out that it's not clear what "Load defaults" loads when using the button when I initially added it to the dashboard in Cornerstone Pages.

Now I'm confused 😅

I also think we're getting a bit carried away with details.

[haqadn]

I think handle is fine considering this terminology is coming WP itself, Example.

[dilirity]

I've updated the UI accordingly in 04a0dfd.

[haqadn]

Looks good to me. I did make some changes. Since I am the one who made the latest changes, leaving the approval to others.

Rationale behind my commit (b2c5854):
I wanted to keep the stores for CSS and JS separate. This will allow us to easily move the store registrations to individual modules, which we need to do soon.