Reorganize frontend design system/components structure

[katyasoup]

Description:

Many shared components like our checkboxes, header/footer, search input, etc are housed within the /query directory, even though they are used elsewhere throughout the app. We should reorganize our file structure and store like with like, so that these shared components are accessible from one level, and page-specific components (like patient result view, or the concept code selection form) live at the same level as their respective pages.

Acceptance Criteria:

• a top-level designSystem directory should house:
  • static components that are re-used throughout the app (header, footer, site alert, etc)
  • dynamic components that are data-agnostic (ex. the Accordion component is a wrapper that takes in content-forward params and puts it in the right data structure that underlying Truss component expects)
• page-level components directories should house:
  • the base page.tsx for next.js routing
  • components that are unique to that page/view
    • ex: query-building components include ValueSetSelection, ConditionSelection, ConceptSelection, each of which pull in shared top-level components like Checkbox, Drawer, etc)

[linear]

QUE-152 Reorganize frontend design system/components structure