Read configuration from LDAP first to guarantee its availability.
    
    All configuration need to be read first so its available during data
    processing. This makes possible to store fake_mname and similar
    variables in LDAP while using them for dynamic entry generation.
    
    New implementation of ldap_syncrepl_watcher() sequentially opens
    two SynRepl connections in different modes:
    1. configuration is synchronized using LDAP_SYNC_REFRESH_ONLY mode
    2. all the data including configuration are read using
       LDAP_SYNC_REFRESH_AND_PERSIST mode
    
    Synchronization state machine (inst->sctx) was extended with new states which
    are used to track progress of configuration & data synchronization. The state
    machine guarantees that configuration is synchronized first and data are
    processed only when all the configuration events were processed.
    
    https://fedorahosted.org/bind-dyndb-ldap/ticket/162