I tested this now on SQL 2019 as well. And indeed, on SQL 2019, this event does not fire. But as I said, it fired on SQL 2022 when I tested.
I guess then that this is a new event, introduced in SQL 2022. Somehow the metadata about the event has leaked into SQL 2019, but the event itself has not been backported.