Reduce boilerplate code in `Change Notifier`-based hooks

[yelliver]

trafficstars

This PR is a continuation of #415 and ensures that:

• No public API is changed or affected
• No new API is published

I want to keep this PR focused on reducing boilerplate code and do not intend to add a complex hook with various life-cycles (this might be done in a separate PR).

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: dcddf2bac7d926339763b9e600ae2c44b5963cc3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[yelliver]

@rrousselGit could u pls take a look?

[rrousselGit]

I appreciate, but I'd rather stick to the current implementation.

The mains are minimal, and we loose a bit in terms of diagnostic and debugging. Using a unique class for all hooks produce better error messages and improves hot-reload a bit.