fix(useTimeoutFn): respect callback parameters in start function

[wvffle]

Description

fixes #2691

Additional context

On L62 of useTimeoutFn, start() is used without any parameters. What if user defines a callback that requires arguments to work? Maybe a new option like defaultArguments could be introduced?

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[wvffle]

@antfu what's your view on the additional context provided in the PR description?

Provided:

const { start } = useTimeoutFn((arg1: string, arg2: number) =>{
  // ...
})

Due to explicitly added [] to the Stoppable type users can do start() without arguments even though they're required.

I've added it explicitly to allow for immediate start. Maybe there should be an option for the arguments passed to the immediate start call?