Klever

At the moment during population all preset jobs and marks are uploaded. For development and testing purposes that is well, but for the production use case users get several redundant jobs and hundreds of redundant marks intended for those jobs. This not only confuses production users but also can cause quite considerable overhead for many operations.

I suggest to have a dedicated setting, e.g. _POPULATE_JUST_PRODUCTION_PRESETS _ that can be either true or false. By default it should be true for the production mode and false for the development one. Because of testing needs the production mode with non-production preset jobs and marks, we can not use the mode as this setting.

Besides, production preset jobs and marks should be explicitly marked, e.g. with Boolean flag production within main preset files, and Bridge should distinguish them appropriately.