IdStory Identity Manager

Currently the initialization of application data is done in bulk in InitApplicationData etc.
The problem here is that both definitions and data are initialized in bulk, which makes separating app into modules quite a feat.
Imagine you have a module specific processor which requires an EAV for IdmIdentity. You initialize this EAV in module's InitMyModuleData.
InitApplicationData creates admin account before your InitMyModuleData is run, so the EAV is still missing, but the module specific processor is already enabled and fails, because it cannot find its EAV.

Idea: split init data to create definitions first and data itself afterwards