refactor: Improve debounce type safety using generics

[yceffort-naver]

This is not related to the changes in this PR, but I have a question regarding the debounce implementation, especially about the return type of func.

Currently, the func argument is typed to return unknown. Is this considered type-safe in TypeScript?
For example, if I pass an async function that returns a Promise<boolean> to debounce, the resulting debounced function’s return type becomes unknown, which requires type assertions or runtime checks when using the return value.
Would it be possible or preferable to type the debounced function so that it preserves the original return type of func, instead of returning unknown?

Originally posted by @yujeong-jeon in #275 (comment)

[yceffort-naver]

The current debounce utility function types the return value of the wrapped function as unknown. This forces developers to use type assertions (e.g., as MyType) every time they use the result, which is inconvenient and reduces overall type safety.