fix(useWebSocket): urlRef changes were not being tracked

[ferferga]

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

URLRef changes were not being tracked inside useWebSocket

[GarlandQian]

If I haven't opened the WebSocket, I believe it shouldn't be opened directly when the URL changes. It should maintain the current state. Even when the immediate parameter is set to false, I think regardless of the current WebSocket state, it should be closed directly.

[ferferga]

@GarlandQian In that case, what's the benefit of using useWebSocket instead of the "raw" WebSocket instance?

This is a regression, not a new feature.