feat: use useEventListener where it was not being used

[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

useEventListener was not being used in all the contexts. With this PR, we're sure the events are correctly disposed always.

Additional context

• Some composables have been refactored a little, given useEventListener simplifies the cleanup logic
• All references to àddEventListener in docs have been updated as well to give the best practices rightaway to users.
• Only 1 usage of addEventListener has been left untouched because it's been removed in refactor(useDevicePixelRatio): use useMediaQuery #4481

[antfu]

I consider this a feature that worth noting in the release note. I am not 100% if this is complete side-effect free when we use this inside a callback. I updated the title.

[ferferga]

@antfu Yes it is (in my app I do use watchers inside Promise.all and other "strange" places and they're garbaged correctly).

This is the only case I found where effectScope is not disabled properly: vuejs/core#12681
In fact, I was thinking at opening a PR at a later time with a new util like tryDispose that checks if there's an effect scope, if not then an appScope, so we toggle between onScopeDispose and onUnmount depending on the situation. But honestly, I prefer to have this fixed in Vue core.