fix(useRouteParams,useRouteQuery): set route param/query to undefined when function-based defaultValue

[henribru]

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.

⚠️ Slowing down new functions

Warning: Slowing down new functions

As the VueUse audience continues to grow, we have been inundated with an overwhelming number of feature requests and pull requests. As a result, maintaining the project has become increasingly challenging and has stretched our capacity to its limits. As such, in the near future, we may need to slow down our acceptance of new features and prioritize the stability and quality of existing functions. Please note that new features for VueUse may not be accepted at this time. If you have any new ideas, we suggest that you first incorporate them into your own codebase, iterate on them to suit your needs, and assess their generalizability. If you strongly believe that your ideas are beneficial to the community, you may submit a pull request along with your use cases, and we would be happy to review and discuss them. Thank you for your understanding.

---

Description

This PR follows up on the changes from #3583. That PR ensured that if you set a route param/query to the default value, it was removed from the query string. However, it doesn't handle function-based default values, so if you set the param/query to the value the default function evaluates to, it remains in the query string. This PR evaluates function-based default before the comparison to avoid that.

Additional context

[henribru]

On second thought, maybe this isn't a good idea. When the default is a function, it could change. If you've explicitly set the query to a value, it might be unexpected for that query to change later if the value you set it to happened to be the default at that time.

[henribru]

On second thought, maybe this isn't a good idea. When the default is a function, it could change. If you've explicitly set the query to a value, it might be unexpected for that query to change later if the value you set it to happened to be the default at that time.

I suppose one way around this could be that when you set the query to the current default value, we still set the internal value, but keep it out of the URL params. We could then watch the default and if it changes to something else than the internal value, we could push the internal value to the URL params. But that's a lot of extra complexity just to keep the URL clean, and it might be surprising to "suddenly" see the value in the URL.