feat(refDebounced): add support for objects

[XavierChevalier]

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.

---

Description

Objects did not work with refDebounced. An object need to be deeply clone to avoid JavaScript memory references.
Added a deep parameter to deeply watch object changes.

Closes: #3158

[XavierChevalier]

Any news on this?

[antfu]

This is not a safe clone, and the result might not be as expected.

Please follow the pattern like this:

vueuse/packages/core/useRefHistory/index.ts

Lines 32 to 39 in 5f58470

	/**
	* Clone when taking a snapshot, shortcut for dump: JSON.parse(JSON.stringify(value)).
	* Default to false
	*
	* @default false
	*/
	clone?: boolean | CloneFn<Raw>

[antfu]

Related to #3705 - I think it's better to design the API and implement on both refDebounced and refThrottled to keep the API consistent