Design shared popover component

[Enjoy2Live]

Considerations
Our components library is missing a popover component, and designers from other teams need to build their custom popovers, which creates visual inconsistencies across Dev Launchers products.

We can see the popover begin used in the notification bell icon when clicked a rich content gets displayed in a portal, but currently it's not being used as a component and doesn't have its own page in the design system figma file.

Acceptance criteria:

• Align the popover component with the existing design system in terms of style, colors, and typography, adhering to established patterns and practices.
• Specify interactions for opening and closing the popover (e.g., on click, hover, focus).
• Design the popover to accommodate various types of content (e.g., text, images, buttons) and include different content variations (informational, interactive).
• Provide design options for positioning the popover relative to its trigger element and offer guidance on auto-positioning for different scenarios.
• Incorporate accessible design practices and WCAG compliance.
• Design the popover to be responsive and adaptable across different screen sizes and devices, with guidelines for varying states and variations (e.g., open, closed, focused, disabled).