eslint: Add eslint-plugin-you-dont-need-lodash-underscore

[anomiex]

Closes MONOREP-11

Proposed changes:

Now that the things the plugin detects have been cleaned up, enable the plugin.

We skip throttle though, as it's more complex than what the plugin's docs claim. The docs only consider the case where trailing: false, which isn't even the default.

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

pdWQjU-1jP-p2

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

No

Testing instructions:

• CI happy?

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the add/eslint-plugin-you-dont-need-lodash-underscore branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/eslint-plugin-you-dont-need-lodash-underscore

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/eslint-plugin-you-dont-need-lodash-underscore

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[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 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 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[anomiex]

Hmm. I missed a bunch using a _ global imported from WP rather than lodash.

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[anomiex]

#44305 for the stuff using the _ global.

[anomiex]

Should be good to review now.

[tbradsha]

Looks good. I was going to ask about fixupPluginRules(), but found you-dont-need/You-Dont-Need-Lodash-Underscore#396, which is fixed by you in you-dont-need/You-Dont-Need-Lodash-Underscore#408. 😄