At this moment, the only way for UserService to handle different user content types is to override hardcoded `userClassId` configuration key even though we had appropriate configuration in adminUI.
This should allow to unify that configuration and to handle multiple user content types for all user service cases.