This supports configuration, when bridge cannot be attached with IPv6 capable
interface (like a lot of WLAN interfaces and IPv6 tunnels).

Thanks to setting ipv6_interface in slapformat configuration file, IPv6
generation will be done there, but IPv4 will be still available on bridge.

Users shall be able to instantiate software instances on their computers. This
is the most often found scenario (add *my* computer and instantiate on *it*
some software).

Add condition to support dictionary. This fix was needed to support Slave Instance inside parameter_dict because each Slave Instance is one dictonary

This commit also  fixes other arguments which were read  and parsed as regular
configuration files.

Previously, cert_file and key_file could  only be set from slapconsole section
but  as it's  supposed to  already been  defined in  slapos section,  then use
slapos values first, then fallback on slapconsole section.

slapconsole  should not fail  when there  is no  "slapconsole" section  in the
configuration file, as defaults should be enough.

slapos.xsd seems package global.

slapformat is small enough to be just one file.

In order to  be able to check  the uniqueness of IPv6 address  assigned to the
bridge,  the  network  interface  must  be up  from  an  administrative  *and*
operational point of view.

However, from  Linux 2.6.39, the bridge  reflects the state  of the underlying
device (e.g.   the bridge  asserts carrier if  at least  one of its  ports has
carrier) whereas it always asserted  carrier before. This should work fine for
"real" network interface, but will not  work properly if the bridge only binds
TAP  interfaces, which,  from  2.6.36, reports  carrier  only and  only if  an
userspace program is attached.

Add support for [slapconsole] config part and aliases (you have variables kvm, mysql, etc, defined from config