fix(smooth-cursor): disable smooth cursor on touch devices

[Yeom-JinHo]

Description

This PR fixes the smooth-cursor behavior reported in #737.
The custom cursor no longer appears after taps on touch/coarse-pointer devices, and the demo/docs now reflect that intended behavior.

Changes

• Added a pointer capability check in SmoothCursor so it only runs on hover-capable fine pointers
• Switched cursor tracking from mousemove to pointermove and ignored non-mouse pointer types
• Prevented the custom cursor from rendering on touch-first devices
• Updated the demo copy to clarify that the component is disabled on touch devices
• Updated the docs to mention that touch-first devices are ignored automatically
• Regenerated the related registry output files

Motivation

Issue #737 reports that the custom cursor appears at the tap position on mobile devices, which creates an unintended visual artifact and hurts the mobile UX.
This change keeps the component limited to environments where a custom cursor is actually appropriate, such as desktop devices with a mouse or trackpad.

Breaking Changes

None.

[vercel]

@Yeom-JinHo is attempting to deploy a commit to the product-studio Team on Vercel.

A member of the Team first needs to authorize it.