**NOT A WORKING COMMIT** Demo purpose branch to show possible solutions to TailwindCSS & Radix UI css variables issue

[chanmSC]

Note This branch is not a working solution, this PR is purely for easy diffs demo/discussion jumping off point of the theme variables management/use issue between TailwindCSS & Radix UI.

Things that need to be discussed/decided:

• CSS module elements would need to be rewritten with purely tailwindcss (not a discussion point, just something important to note)
• How to resolve the theme issue?
  • Should we combine style.css to export both the tailwindcss and radix css variables?
  • Do we need 2 separate CSS files for exported theme styles and docs styles?
  • What should be the procedure for overwriting theme variables?
• Some components aren't exporting/built
  • i.e. import { Badge } from '@australiansynchrotron/sci-comp-ui'
  • Can notice the missing exports from index.es.js (as in they're not there)
• What happens when we have a custom version of an existing Radix component?
  • i.e. Buttons, Form Inputs
  • Should we prefer non-radix components, as they're less likely to visual/behaviourally change based on 3rd party (Radix UI) decisions
  • Should we agree on sth like Radix can be used for components without an existing custom component, and in situations where it's less of an issue if we need to upgrade Radix and they change those components visually/behaviourally)?
• Should we be doubling up on Radix UI component docs?
  • Should we prefer non-radix components in the docs?
  • We should make a decided distinction between what components go into sci-comp-ui docs, and what we leave for ppl to refer to radix-ui docs?