Looks like this is an issue with the migration to 1.6 of collectives which may persist if updating to Nextcloud 25 and collectives 2.0.0 afterwards.
This comment has a workaround for enabling collectives again:
Also 2.1.0 with a fix will be published asap.