feat: lighter build by rewriting lodash imports

[regisb]

Incorrect lodash imports are causing MFEs to import the entire lodash library. This change shaves off a few kB of every MFE compressed build.

[openedx-webhooks]

Thanks for the pull request, @regisb!

This repository is currently maintained by @openedx/2u-tnl.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[regisb]

Issues are not related to this PR. This is ready for review.

[bradenmacdonald]

Thanks! LGTM but let's get a green build before we merge.

[regisb]

Can you help me to figure out what's going on with the build? As far as I understand, other PRs in this repo face similar errors.

[bradenmacdonald]

Not sure if these are all the issues, but these are some of the things causing test failures. If you rebase you'll also get some improvements that make the tests more robust, from the React 18 PR that recently merged.

[bradenmacdonald]

No problem. I actually tried to do a PR like this once myself, but ran into some challenge and move on to other things. So I'm glad to see you tackling it. Looks like you're down to only 1 failing test now :)

[codecov]

Codecov Report

Attention: Patch coverage is 96.80851% with 3 lines in your changes missing coverage. Please review.

Project coverage is 93.54%. Comparing base (a43027b) to head (1d9fff6).
Report is 11 commits behind head on master.

Files with missing lines	Patch %	Lines
...components/EditProblemView/SettingsWidget/hooks.js	90.90%	1 Missing ⚠️
...Widget/settingsComponents/GeneralFeedback/hooks.js	0.00%	0 Missing and 1 partial ⚠️
src/editors/data/redux/problem/reducers.ts	75.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1772   +/-   ##
=======================================
  Coverage   93.54%   93.54%           
=======================================
  Files        1136     1136           
  Lines       23205    23205           
  Branches     5000     4999    -1     
=======================================
  Hits        21708    21708           
- Misses       1421     1429    +8     
+ Partials       76       68    -8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[regisb]

OK I think there might have been a flaky test... This should be good to merge now.