shadcn/cli compatability

[debuggingfuture]

• restructure repo first DAPPK-53

• move out components from storybook

• schema setup

• deps - generate?

• cli testing

• Note how shadcn work

  • https://github.com/shadcn-ui/ui/blob/2f869a2590e90f79890e6fa00cbfcbf8a241b034/apps/www/public/r/styles/default/form.json#L4

_{Huly®: DAPPK-43}

[debuggingfuture]

problem statements

• We want to use different paths for built in shadcn components vs geist components
• We want to avoid maintain copy / submodule of original shadcn
• We need nested components

Current approach

• Modified from build-registry.mts
• support shadcnRegistries to remap deps
• support nested folder

turn out we need to maintain dependencies in registry-ui.ts etc quite explicitly as in shadcn

for now it is better to stack with namespacing components with snake case in file name over nested folder
e.g. identity_address-badge

seems shadcn do not have good support for nested folder e.g. ui/identity/address-badge.tsx

• using name as identity/address-badge we're able to generate the .json and folders,
  however at install it will be ignored and always write to ui/address-badge.tsx

target field in generated .json can override that but it is very forceful and do not honour the alias configured in componetns.json