Clean up dependency specifications

[bradenmacdonald]

Upgrade PRs like openedx/frontend-app-learning#934 are currently blocked because this plugin is overly specifying its dependencies. There were also a number of other problems which I've fixed - see inline comments.

npm warn Could not resolve dependency:
npm warn peer redux@"4.1.2" from @edx/frontend-lib-learning-assistant@2.2.4
npm warn node_modules/@edx/frontend-lib-learning-assistant
npm warn   @edx/frontend-lib-learning-assistant@"^2.2.4" from the root project

[bradenmacdonald]

These font awesome dependencies aren't even used.

[bradenmacdonald]

core-js is not needed in 2024.

[bradenmacdonald]

These deps are all specified by the learning MFE and are already in peerDependencies so they don't also need to be in devDependencies.

[bradenmacdonald]

regenerator-runtime is not needed in 2024.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.14%. Comparing base (ce3677d) to head (5aed7e5).
Report is 15 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #63      +/-   ##
==========================================
+ Coverage   81.36%   82.14%   +0.77%     
==========================================
  Files          13       18       +5     
  Lines         220      280      +60     
  Branches       30       52      +22     
==========================================
+ Hits          179      230      +51     
- Misses         39       48       +9     
  Partials        2        2              

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

[bradenmacdonald]

@rijuma @alangsto Could you please take a look at this?

[alangsto]

This looks good to me, thank you!

[bradenmacdonald]

Thanks @alangsto! I will need someone on your side to merge this whenever ready.

[alangsto]

@bradenmacdonald I can go ahead and merge this now, but because the commit type is chore, merging this PR will not trigger a semantic release. If that's fine, let me know and I will merge! Otherwise, feel free to update the commit type to something that will trigger the release, and I can merge after that.

[bradenmacdonald]

@alangsto Good point; changed to fix :)