fix(perf): replace legacy NotesHooks boot registration with typed file event listeners

[joshtrichards]

Summary

This refactor:

• avoids unnecessary LazyFolder materialization during app boot
• modernizes startup by removing the remaining legacy filesystem hook registration

It does so by migrating note metadata invalidation from legacy hooks to typed filesystem event listeners.

Why

The previous implementation registered listeners by calling listenTo() on a lazy root folder during boot(). That pattern can eagerly initialize IRootFolder just to register listeners, defeating laziness and adding avoidable request-time overhead.

Using registerEventListener() in Application::register() makes listener registration declarative and avoids boot-time access to the lazy filesystem root.

This is intended to address #1835 and is also a worthwhile cleanup on its own to move Notes away from legacy hook APIs (and since it'd be really really nice to drop support for the old hooks upstream at nextcloud/server).

Changes

• removes the legacy NotesHooks registration pattern from Application::boot()
• registers typed filesystem event listeners in Application::register()
  • these are 1:1 equivalents of the old hooks
• adds NoteFileEventsListener to handle note metadata invalidation for the events formerly handled by NotesHooks
• removes obsolete Psalm baseline entries related to NotesHooks

Behavior

This refactor is intended to preserve the existing invalidation behavior:

• write/touch/delete invalidate metadata for the affected node
• rename invalidates metadata for the source node

Expected impact

• avoids boot-time lazy folder materialization
• aligns Notes with modern Nextcloud event registration patterns
• reduces per-request overhead caused by legacy filesystem hook setup

Notes

• Closes [Bug] Notes app boot() forces LazyFolder materialization on every request causing severe performance degradation #1835
• Backporting: this is arguably a bug fix, even if the same change would likely have happened later as part of retiring legacy hooks

[CarlSchwan]

Yeah for less legacy hooks \o/

but please wait for one of the maintainer of the app to approve before merging