refactor(core): narrow types in debounce utility

[guesung]

Summary

• Narrow types in debounce.ts to reduce any usage
  • pendingThis: any → ThisParameterType<F> | undefined
  • debounced function this context: any → ThisParameterType<F>
• Keep any[] in generic function constraint (F extends (...args: any[]) => void) — required due to parameter contravariance (unknown[] rejects callbacks with specific param types like (value: string) => void)
• Replace file-level eslint-disable with inline eslint-disable-next-line on the two lines that need it

[Copilot]

Pull request overview

This PR refactors the core useDebounce utility’s internal debounce.ts typings to remove any usage and better model this context for debounced functions.

Changes:

• Narrowed the generic function constraint from any[] to unknown[].
• Typed pendingThis and the debounced function’s this parameter using ThisParameterType<F>.
• Removed the file-level eslint-disable @typescript-eslint/no-explicit-any comment.

[Copilot]

The F extends (...args: unknown[]) => void constraint is too strict under strictFunctionTypes: a typical callback like (value: string) => void does not satisfy it (because string is not a supertype of unknown). This makes DebouncedFunction<typeof callback> unusable for most typed functions and will likely break downstream typechecking. Consider reverting the args constraint to any[] (with a localized eslint disable) or using a different “any function” helper type that still accepts specific parameter types.

[Copilot]

Same issue as the DebouncedFunction type: constraining debounce with F extends (...args: unknown[]) => void rejects most typed callbacks (e.g. (value: string) => void) in strict mode, which can break internal callers and public API usage. Please loosen this constraint so typed parameter lists are accepted.