This seems like your standard open core/dual licensing, CLA controlled BS where open source is indeed treated like an inconvenience... Perhaps with more obfuscation than on average. Probably not really adding requirements on top of AGPL as such but they seem to be offering multiple releases under a more restrictive license either because they have the rights so they can do dual licensing or they keep certain components proprietary and don't offer those with the team/community editions.

So yeah, probably within their legal rights and I assume there is still a codebase/release that you can use under the terms of the AGPL but they do seem to be looking for ways to make it be used as little as possible.

I could be wrong if the AGPL and other open source parts aren't enough for actually compiling a functional version of this but this is what it mostly looks like to me.