Refactor Tooltip component

[buberdds]

Closes #24

https://pr-27.oasis-ui.pages.dev/?path=/docs/components-tooltip--docs&globals=theme:light
vs current
https://oasis-ui.pages.dev/?path=/docs/components-tooltip--docs&globals=theme:light

• adjust styles
• add interaction to play function (hopefully this is will be used in regression tests more in the future)
• API changes:

<Tooltip title="Tooltip content">
  <Button variant="outline">
    Hover me
  </Button>
</Tooltip>

instead of

<Tooltip>
  <>
    <TooltipTrigger>
      <Button variant="outline">
        Hover me
      </Button>
    </TooltipTrigger>
    <TooltipContent>
        Tooltip content
    </TooltipContent>
  </>
</Tooltip>

[github-actions]

Deployed to Cloudflare Pages

Latest commit:	8812c6a3dc48b5a3f0c32f34d35be555081eb19c
Status:	✅ Deploy successful!
Preview URL:	https://5bb42d94.oasis-ui.pages.dev
Alias:	https://pr-27.oasis-ui.pages.dev

[lubej]

I am not in favor of modifying the original components of shadcn. As the docs we will be referring to are still the original dev docs. I would rather see we would create wrapper version of the component. Especially if we are going to use generation tools, which would always generate "wrong" tooltip, and would always require manual changes. Can we maybe discuss this in more detail on next FE sync, on how to manage "custom" components?

[buberdds]

Sure let's chat tomorrow.

For now I can bring back original tooltip and add wrapper as a separate component. For generation tools no clue how they gonna work.

[buberdds]

For Sync meeting:

1. how we want to handle custom components (where to store them/naming convention/export names etc).
   For clear separation maybe current componets/ui would be more like base components (not imported) in apps?

2. what are boundaries of auto generated components customization?