refactor: transitions and animations to tailwind

[JammingBen]

The few complex transitions are still written in pure CSS, I don't feel like it would be fun (or even possible) to write them via Tailwind classes.

refs #937

[Copilot]

Pull Request Overview

This pull request refactors the codebase to use Tailwind CSS classes for transitions and animations instead of custom CSS. The purpose is to standardize animation and transition patterns while maintaining the visual behavior of the UI.

• Replaced custom CSS transitions with Tailwind utility classes
• Moved animation keyframes from individual component styles to a centralized location
• Updated test snapshots to reflect the new class names

Reviewed Changes

Copilot reviewed 36 out of 36 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
design-system/src/styles/tailwind.css	Added centralized animation keyframes (shake, shimmer, loading-bar)
design-system/src/styles/layers.css	Added transition classes to oc-card component
design-system/src/components/*/	Multiple components updated to use Tailwind transition classes
web-runtime/src/components/	Transition classes updated in navigation and notification components
web-pkg/src/components/	Various sidebar and filter components updated
test snapshots	Updated to reflect new Tailwind class names

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}