Add configurable animation overrides and smooth transitions

[Abeansits]

Summary

• Adds optional openingAnimation, closingAnimation, conversionAnimation properties to DynamicNotch — when set, they override the style's default animations. When nil (the default), behavior is unchanged.
• Adds smoothTransition boolean — when true, expand() and compact() skip the intermediate hide step, converting directly between states for a faster, more fluid transition.
• Makes isHovering publicly readable (public private(set)) so consumers can react to hover state changes.

All changes are additive and backwards-compatible. Existing consumers see no behavior change.

Motivation

When building an app that lives in the notch and toggles between compact/expanded on hover, the default expand() → hide → re-expand flow adds ~250ms of unnecessary delay. smoothTransition = true skips this, and custom animation durations allow tuning the feel for different use cases (e.g., snappier for interactive UIs, slower for notifications).

Making isHovering public enables reactive patterns like expand-on-hover without resorting to workarounds like NSEvent monitors.

Test Plan

• swift build passes with no warnings
• Verify default behavior unchanged (no properties set)
• Verify smoothTransition = true skips hide step on compact↔expanded
• Verify custom animation overrides are applied
• Verify isHovering is readable from consuming modules

[Abeansits]

@mrkai77 lemme know if you're open for this change, I think it gives users nice control over the animation

[mrkai77]

Hey @Abeansits, this is definitely a welcome change!

The only thing I’d suggest is that, instead of providing an override for each animation individually, we introduce a dedicated struct called DynamicNotchTransitionConfiguration, with a default animation for each transition set in its initializer. I think that would help keep things more organized and make the API a bit cleaner.

I’d also recommend renaming smoothTransition to skipIntermediateHides, as that's a bit more descriptive of what it controls (and this can also move into DynamicNotchTransitionConfiguration).

Let me know if you’d like me to elaborate on any of this!

[Abeansits]

@mrkai77 those were reasonable comments! let me know your thoughts

[Abeansits]

you good to merge now @mrkai77 ?

[mrkai77]

Sorry I missed your comment! Yes, this is all good to merge now.