Split docs into primitives and composed components

[H4ad]

Split between Simple (presets) components and the primitive versions that needs to handle everything manually.

[rinkydevi]

@H4ad thanks for this , will be working on it

[H4ad]

@rinkydevi for this one, we can start by structuring the menu on storybook and them we organize the code.

Today we have two sections, design system and components.

We can likely rename components to be "Composed Components", and then have the "ComboboxSimple", "SelectSimple", etc... (maybe we can think in a better name for them, today almost all of them are under the presets folder under the component name)

And then we can have the "Primitive Components":

• Switch
• Typography
• Dialog
• Etc...

The idea is:

• Composed Components: they have a lot of built-in functionality, like ComboboxSimple you can simply pass items prop, and to have manual control, you can use ComboboxItem/ComboboxList/etc...
• Primitive Components: they are the base layer of a complex component or just a component that does not have much complexity, eg: Switch, Typography, Input, Button, Badge, etc...

To start this issue, you can first create a summary of what we will put in the Primitive and what will be Composed (eg: Calendar is composed component or primitive?).

After knowing the category of everything, we can update the docs