Create new informational side panel for hybrid learning view

[marcellamaki]

Overview:
The new side panel component is used to display resource information and lesson plan information.

Done when:

• Side panel can be toggled open and closed (note: this can be a last TODO for when the menu bar is merged)
• Side panel has the appropriate new mobile-responsive breakpoints laid out in figma
• Side panel content is rendered either as information panel or as lesson/topic panel
• As an information panel:
  1. The resource title, description, subject, level, language, author, license holder, and license details are visible and displayed in line with the figma design
  2. Long descriptions should be truncated to fit within a "preview" 170px high, and have an option to toggle to read more (with scroll) and then read less
  3. The license details should default to being collapsed, and similarly have a toggle to display that metadata
  4. There should be a button at the bottom of the panel to download resource, and this interaction should be implemented as part of the PR
• As a topic/lesson panel:
  1. Each related (previous/next resource) should be listed in order
  2. The current resource should be indicated as current with a shaded background (as indicated in design)
  3. Basic metadata of the title of the activity/resources and an icon should be displayed, with tooltips
  4. Empty topics should render with a "no more topics" message (see figma references)

Beyond scope of this ticket:

• Creating the "chips" seen at the top of the info panel
• Side panel implemented in other place in the code base
• Interactions to navigate between topics/resources in the side panel (as this needs further clarification)
• Display of metadata related to progress, completion and estimated time

NOTE:

• Any metadata that is within the scope of this ticket but not available should be noted and raised for discussion to clarify the timeline of when it can be included. TODOs should be included in the code as well to keep track, and outstanding items should be referenced in the PR.

Figma references:

[marcellamaki]

Still to do:

• make sure that all of the design use cases are covered by existing components and updated as necessary
• responsiveness

[nucleogenesis]

Much of this is covered in #8466 but the metadata is not available, so this won't be finished until metadata is available.