feat: support design tokens and paragon 23

[dcoa]

Warning

This PR should not be merge to master directly, it should point to master-design-tokens once the branch has been created.

Description

This PR updates frontend app account to support CSS variables and the corresponding paragon design tokens.

Changes implemented:

• Replace Paragon SCSS variables with CSS variables.
• Replace deprecated components Input, ValidationFormGroup

Important

This PR requires a compatible version with paragon 23 of dependencies because of that the following PRs need to be merged first:

• feat: adds support for loading external theme CSS for MFEs  frontend-platform#689
• feat: update dependecies that support css variables frontend-plugin-framework#105
• [BD-46] feat: added support Paragon design tokens frontend-component-header#351
• [BD-46] feat: added support Paragon design tokens frontend-component-footer#303

[openedx-webhooks]

Thanks for the pull request, @dcoa!

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

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.57%. Comparing base (17e12f7) to head (54693d0).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1198      +/-   ##
==========================================
+ Coverage   58.53%   58.57%   +0.03%     
==========================================
  Files         117      117              
  Lines        2320     2322       +2     
  Branches      639      643       +4     
==========================================
+ Hits         1358     1360       +2     
  Misses        901      901              
  Partials       61       61              

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

[dcoa]

I'm not 100% sure why used to work (or why after updating paragon is not working) but q is not direct children or article because is wrapped in a div, here the render:

    <body>
      <div>
        <div
          role="article"
        >
          <div>
            PluginSlot_
            <div>
              <q
                role="note"
              >
                How much wood could a woodchuck chuck if a woodchuck could chuck wood?
              </q>
            </div>
          </div>
        </div>
      </div>
    </body>
```

[brian-smith-tcril]

Yeah, based on the name of the test

renders as the slot children directly if there is content within

it seems like the test should be failing from a "it's not directly rendering the children, it's wrapping them in a couple layers of divs" perspective on latest master too. I double checked and got the same render output on latest master.

MockedPluginSlot is absolutely not behaving in the way that

renders as the slot children directly if there is content within

expects.

Since this is only testing a mock component, I think the best path forward here is to make an issue documenting the discrepancy and use your minimal change to get tests passing again as-is for this PR.

[dcoa]

I created the corresponding issue in the MFE repo

[open-craft-grove]

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[open-craft-grove]

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[open-craft-grove]

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[open-craft-grove]

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements