Add Liquid glass card

[Katotodan]

Notes for Reviewers
This PR introduces a new LiquidGlass UI primitive to the Sistent library. The component provides a reusable “liquid glass / glassmorphism” effect that can be used as a container for content while preserving readability and visual depth.

Features

1. Frosted glass effect using backdrop-filter (blur + saturation)
2. Optional “overLight” mode for light backgrounds
3. Optional shadow toggle (showShadow)
4. Customizable:

• blurAmount
• saturation
• cornerRadius
• padding

Implementation Notes

• The glass effect is isolated in a dedicated backdrop layer to avoid blurring child content.
• Defaults are provided to ensure the component works out-of-the-box while remaining customizable.

This PR fixes #1238

Signed commits

• Yes, I signed my commits.

[Katotodan]

While developing, I tried this component inside a simple react app to see the output.
Here is the demo

Screen.Recording.2026-02-11.at.16.58.03.mov

Here is a screenshot of code for the above react app visualization.

[Katotodan]

I have also tried it with layer5 website locally.

Screen.Recording.2026-02-11.at.17.02.10.mov

Here is a portion of layer5 main page code with the LiquidGlass component on it

The zIndex is customized (and other properties as well).

[leecalcote]

We have something similar on www.kanvas.new now., so the concept is viable.

[Katotodan]

We have something similar on www.kanvas.new now., so the concept is viable.

Thank you for the clarification @leecalcote.
Just to confirm, does this mean the component direction is appropriate as implemented, or would you prefer that I align it more closely with the version currently on kanvas.new?
Based on the issue description, I took inspiration from the liquid-glass-react reference repository (https://github.com/rdev/liquid-glass-react) and implemented the feature following that concept. I’m happy to refine it further if needed.

[Bhumikagarggg]

@Katotodan Thank you for your contribution! Let's discuss this during the website call tomorrow at 6:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂

[leecalcote]

@Katotodan go forth with instrumenting this as an optional style in various existing components.

[Rajesh-Nagarajan-11]

Any Updates @Katotodan ??? Ready for Review ???

[Katotodan]

Not yet @Rajesh-Nagarajan-11
I am still communicating with Mr @leecalcote on how to better implement this feature.

[banana-three-join]

It should be fine to merge as improvement is only going to appear once the component is tested in real use cases. It being optional allows for quick switching in case it's behavior is too unstable as it keeps on being improved on.