New CLI discovery and build for Code Components

[#3571534]

• outdated manifest.json
• Updated canvas-manifest.json sample here: https://gist.github.com/harumijang/5fe0bebf911e75637bcfecd9fffd2c92. This removes global and components key and adds a new font key.
• Output directory structure
  • /dist/components - All components no matter where they live in the user's codebase
  • /dist/local - All local imports with path structure preserved in the output in order to avoid collisions of the same file name. (e.g., 'dist/local/component/hero/utils.js', 'dist/utils/utils.js')
  • /dist/vendor - All third party imports (including fonts)
  • /dist/index.css - Tailwind global css
  • /dist/index.js - Tailwind global js classnames
  • /dist/canvas-manifest.json
• Added typescript support to CLI but we should add it here too for the Canvas code editor https://www.drupal.org/project/canvas/issues/3562289

✅= addressed

❌= not yet done

1. Discover all components — no support needed for partial builds.
2. Implement support for the following imports:
   1. ✅ Third-party import: import { motion } from "motion/react"
   2. ✅ Local module import
      1. from an arbitrary shared location: import { formatDate } from "@/lib/utils"
      2. from a component's directory: import { formatPrice } from "@/component/pricing/helpers"
   3. ✅ Image asset import: import heroImg from '@/components/hero/hero.jpg'
   4. ✅ SVG import as a React component using SVGR: import CartIcon from '@/components/cart/cart.svg
   5. ✅ CSS as side-effect imports only:
      1. local: import '@/utils/styles/carousel.css'
      2. third-party: import '@fontsource/inter'
3. ✅ Keep the compilation of the discovered Code Components the same as before.
4. ✅ Keep using tailwindcss-in-browser for building the CSS.
5. ✅ Introduce an optional config file (e.g. canvas.config.json) to allow configuring the followings:
   1. directory to use as the root for resolving the import path aliases. (default to src)
   2. build output directory (default to dist)
6. ✅ Generate and place a manifest file to the build output directory to track the path to each Code Component (JS source, CSS source, and component.yml), as well as all files put in the build output directory.
7. ✅ Tests
8. ✅ Adding @drupal-canvas/vite-compat and @drupal-canvas/discovery to cli/package.json. It is using those packages but not yet in package.json. Node was complaining about the entry points of those two packages being typescript so it couldn't resolve them.