Add typed events for all user hooks and legacy events

[ChristophWurst]

Update

see #18348

---

• Add typed events
• Emit events where we emitted legacy events and/or hooks
• Catch new events and re-emit data as legacy events and/or hooks

-> existing code should continue to work, but new code can use the typed events with 18+

• Session https://docs.nextcloud.com/server/stable/developer_manual/app/hooks.html#session
  • preSetPassword (\OC\User\User $user, string $password, string $recoverPassword)
  • postSetPassword (\OC\User\User $user, string $password, string $recoverPassword)
  • changeUser (\OC\User\User $user, string $feature, string $value)
  • preDelete (\OC\User\User $user)
  • postDelete (\OC\User\User $user)
  • preCreateUser (string $uid, string $password)
  • postCreateUser (\OC\User\User $user)
  • preLogin (string $user, string $password)
  • postLogin (\OC\User\User $user, string $password)
  • logout ()
• UserManager
  • preSetPassword (\OC\User\User $user, string $password, string $recoverPassword)
  • postSetPassword (\OC\User\User $user, string $password, string $recoverPassword)
  • preDelete (\OC\User\User $user)
  • postDelete (\OC\User\User $user)
  • preCreateUser (string $uid, string $password)
  • postCreateUser (\OC\User\User $user, string $password)

Note: I don't get the diff between Session and UserManager hooks as we always emitted on the manager.

[rullzer]

quick 🚬-test
looking good. Lets do this 🚀

[ChristophWurst]

rebased to resolve conflicts

[ChristophWurst]

updated to fix tests

[skjnldsv]

Houston, We have a liftoff 🚀

[MichaIng]

This solves #18331, right?

[ChristophWurst]

This solves #18331, right?

Nope. The uses of the old event are still a problem in some cases. I'll try to have a look at that as well. The problem is that we can't migrate those without introducing a breaking change 😢

[MichaIng]

@ChristophWurst
Okay, if it does not cause issues now, hence does not require urgent action, it is probably best to omit those logs, to not flood log files?

[ChristophWurst]

Those logs are fine. You only see them with log minimum log levels set.

We want them to be visible for app developers so they take action timely. On production instances these lines won't show up.

[MichaIng]

@ChristophWurst
It is currently log level 1 (info) at least, not "minimum" log level 0 (debug). Does it make sense to report it to re individual apps repos then? Not sure how quickly different developers test NC betas 😉.

[ChristophWurst]

It's not just about the apps. As long as we emit the legacy event for BC reasons this info log will be shown.

[ChristophWurst]

Can't make CI happy here. #18348 is a simplified version for 18. Cleanup has to follow later.

[gary-kim]

@ChristophWurst Can we close this now?