Ok replying to self, the models are documented here and it seems nothing has changed in the lifcycle hooks themselves.
But something has changed in respect to that the afterSearch hook is no longer triggered when browsing around in the content-manager url, example /admin/plugins/content-manager/collectionType/application::myitem.myitem
So I cannot use these hooks any more to “trick” Strapi into displaying fields that are calculated on the fly, in the pager / list view.
Are there any guidelines to override this behavior or bypass any “caching” that Strapi is doing now, that it wasn’t doing in v3.1.6? I am a bit lost…