feat: add ProgramList page

[MaxFrank13]

Program Page

Adds the Program List page. This renders a Paragon Card component for each Program that the learner has enrolled in. There is also a call-to-action component that directs users to the open courses search page. This page is locked behind the ENABLE_PROGRAM_DASHBOARD configuration variable. See below for more details on what's included in this PR.

Legacy view in edx-platform:

New view in Learner Dashboard:

Enterprise view from frontend-app-learner-portal-enterprise that was used for prior art:

Covered in this PR

Adds the ENABLE_PROGRAM_DASHBOARD environment variable

• We could in theory use the ENABLE_PROGRAMS environment variable that already exists
• Using the current variable is nice because it means one less variable to monitor; it is however potentially problematic if a consumer wants to enable programs but still use the old dashboard

Add a Program Dashboard route as well as a Program Details route

• We need two routes to render two different views at their own URL
• They are both locked behind the ENABLE_PROGRAM_DASHBOARD environment variable

Adding Routes required that some modifications be made to other parts of the code

• Previously, the Dashboard homepage was treated as the sole page for Learner Dashboard, see changes where <AppWrapper /> and <FooterSlot /> both previously resided in the App.jsx file. The App.jsx file is what controls the rendering of the Home page (it should probably have a different name)
• <AppWrapper /> did literally nothing but pass through the children -- see this PR for original intentions. Those intentions are rendered obsolete with frontend-plugin-framework and the eventual arrival of frontend-base -- it's been removed completely.
• <FooterSlot />, as well as all of the Routes, now live in the index.jsx file

Removing NoticesWrapper -- this is something that will be done upstream by the time this Program Dashboard is set to merge there

• It can be safely ignored in this PR as it does nothing to the ProgramDashboard
• It was removed while adding the routes

[deborahgu]

this looks great to me. A couple of things we discussed while we paired over this:

• when you PR to master we can discuss with Axim about different proposals for making this optional during a depr period, including:
  • waffle flag
  • putting a plugin slot around the header, so people can replace the header with one that just links to the legacy page
  • not bothering, because the only instance that deploys off of master doesn't use the program dashboard, and we are doing a one to one replacement
• in a later PR you are planning on adding an error response to the API exception handler