Fixed handling of zones (import/read)

- bnc#898659
- Checking for system zones was moved to separate function
- Extended list of zones marked as system (internal) ones with (0\.)+ip6.arpa
- Not allowing to edit system zones (belong to bind package)
- Added check for 'bind' package to be installed before writing the configuration
- Marking all imported zones as 'modified' to be written later
- Marking all imported non-system zones as 'is_new' to create a zone file for them
- Flushing /etc/named.conf cache 'after' writing zones (instead of 'before')
- Using "" as the default NETCONFIG_DNS_POLICY (instead of 0)
- Do not write system zones to LDAP (bnc#746401)
- If systems zones are marked as modified, they are written to named configuration (if LDAP is not in use)
Which modes? Aaaah, do you mean `Mode.config`, as checked in `CheckAndInstallPackages`?
That check is supposed to mean "an AY module declares that it need these packages, but we do not need to install them if we are just editing a profile to be applied elsewhere". Now, if we use the Apply feature of the AY UI, the packages *will* need to be installed, but it should be the AY UI to temporarily change the mode, not the individual modules.