feat: make this app compatible with rsbuild

[regisb]

The webpack configuration used to include a weird line, that allowed all
non-implicit imports from src/. Such imports were ambiguous, and
required modification of the resolve path, which is unconventional.

To resolve this, we adopt the same solution as frontend-app-learning:
src/ imports are written as from '@src/...'.

[openedx-webhooks]

Thanks for the pull request, @regisb!

This repository is currently maintained by @2U-aperture.

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.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.43%. Comparing base (a210f23) to head (9256877).
⚠️ Report is 61 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #598   +/-   ##
=======================================
  Coverage   97.43%   97.43%           
=======================================
  Files         152      152           
  Lines        1327     1327           
  Branches      219      219           
=======================================
  Hits         1293     1293           
  Misses         33       33           
  Partials        1        1           

☔ 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.

[itsjeyd]

Hi @regisb, are you planning to continue working on this PR, or is it perhaps no longer needed?

[regisb]

If people agree on the suggested approach here, then I can update the PR and rebase it on top of master. I have added a PR description to make it clear what this is all about.

To clarify: the rsbuild PR depends on this one, but this PR is a win in all cases, because it simplifies the webpack configuration of the learner dashboard MFE.

[itsjeyd]

Thanks @regisb.

@openedx/2u-aperture This PR is still in draft state but could you please give it a first look and see if you're good with the general approach?

[MaxFrank13]

Thanks @regisb.

@openedx/2u-aperture This PR is still in draft state but could you please give it a first look and see if you're good with the general approach?

This approach looks good to me. The way it is currently set up definitely can cause some confusion and this change will make it easier to grok.

I notice that the webpack.prod.config file for this MFE is different than the one for the Learning MFE when it comes to handling the @src alias. Would we want these to be consistent with each other? It seems like two implementations to accomplish the same thing from what I can tell, but perhaps I'm missing something.

Thanks for the contribution, @regisb!