Compass layout support

[kmcfaul]

POC branch:
patternfly/patternfly-ai-coding#3

Compass CSS:
src/components/lib/css/compass.css

Follow up epic:
#269

1. Problem Statement & Goal
   Delivery of new components and PatternFly component updates resulting from the Compass PoC AS A PRERELEASE. The goal is to allow product teams to begin pulling in these new components and updates to use in PoCs as soon as possible, giving design and product an opportunity to provide feedback and iterate on the eventual new theme, and ensure integrating PatternFly with the development of future designs in product.

2. Scope & Completion
   Scope is the implementation and delivery of the new layout components and existing component updates as defined by sub-issues created from the PoC. Delivery will be as a prerelease of PatternFly at the end of the sprint. Iterating with design and applying feedback will be represented and enacted in a follow up epic.

Icons are not a part of this epics deliverables - any needed icons may be inlined into demos as required.

3. Risks & Testing (likely these will not be addressed in the first pass & sprint, see follow up epic TBD)

• Mobile layout not yet designed.
• Other design work covering components or views outside of original PoC scope, and/or changes to look and feel post-PoC, may impact scope of this epic.
• A11y and keyboard navigation audits should be completed as part of this epic and may impact scope depending on any found issue(s)' severity.
• Newly added components/package should use the beta label to allow restructuring of API and component structure after first delivery pending architecture review.
• Glass css styling is somewhat tricky and limiting (has problems with other element's z-index, transforms, layered glass effects, etc).
• Tailored/audited high contrast support out of scope for this epic.

4. Supporting Information & Communication

• A new 'handbook' under developer resources (for now) and is live on staging (not published PF.org yet) which includes:
  • explains how to wire up these new components and themes (if they should leverage use context, if they need to pull in a new stylesheet, etc).
  • some of the screens as full screen demos.
  • information about how to integrate with react-flow if applicable.
• Other communication TBD.

5. Effort & Open Questions
   Open questions are mostly represented in Risks.