feat: add interaction enhancements for One UI 8.5

[xrzcc]

Why

One UI 8.5 on Android 16 still requires extra gestures for several common interactions: opening Finder from the middle of Home, completing an additional swipe after lock-screen authentication, and manually reopening apps after a restart. Notification wake behavior and lock-screen swipe distance also have no fine-grained user controls.

This change provides opt-in interaction controls for rooted devices while preserving Samsung's authentication checks and original behavior whenever a hook cannot be resolved.

What Changed

• Add a dedicated Interaction enhancements category with detailed descriptions, live slider values, system haptic feedback, and optional main-menu category hiding.
• Add One UI Home gestures for middle-screen swipe-down Finder launch with automatic keyboard focus, while preserving the notification-shade gesture.
• Add System UI hooks for configurable lock-screen swipe distance and direct notification opening only after the system reports the lock screen can already be dismissed.
• Add notification-triggered screen wake with a configurable 1–10 second duration and filtering for ongoing, summary, self, and already-screen-on notifications.
• Add a KernelSU-style zygote soft restart action with confirmation.
• Add opt-in post-boot and post-soft-restart launching for selected user-installed apps through a persisted one-shot job and root.
• Add diagnostics, compatibility-safe preference defaults, serialization tests, localized UI strings, bilingual Chinese/English README documentation, and implementation notes.

All new behavior defaults to disabled.

Verification

• Built and installed successfully on a rooted Samsung SM-S942U1 running Android 16 / One UI 8.5.
• Manually validated lock-screen swipe scaling, Finder keyboard focus, notification wake duration, authenticated notification direct opening, menu hiding, soft restart, and selected-app auto-start behavior.
• Verified the boot receiver schedules a one-shot persisted job, respects the disabled state, and leaves no repeated job after completion.
• Existing preference payload compatibility and new auto-start selections are covered by unit tests.