Support unpublished variant doc types on content type service in brX SaaS

It is decided that in the first phase single developer project will be supported instead of multiple developer projects on document types in brX SaaS. Unpublished variants of document types will be used like the developer branch.

On document editor, channel manager and visual editor, when active developer branch is selected, then the unpublished variant of the doctypes/compoundtypes should be loaded.

To be able to support unpublished doc type variant on editors content type service needs to be updated. Content type service is going to store published and unpublished doc type variants.

It is also required to update dynamic beans since the generated beans are cached with content types.