Bootstrap agent2 support (continued) - Waiting for postgresql fix

[Phil-Friderici]

In this PR I try to continue the work of fe80 (and others) in PR824.

Pull Request (PR) description

This Pr bootstrap a support for zabbix-agent2

• Add param binary_location for specify zabbix agent binary (only for systemd)
• Remove some parameters in zabbix agent configuration if it's zabbix agent2 package
  • LogRemoteCommands
  • StartAgents
  • MaxLinesPerSecond
  • AllowRoot
  • User
  • LoadModulePath

It's possible to use agent2 with this configration:

      'agent_configfile_path' => '/etc/zabbix/zabbix_agent2.conf',
      'include_dir'           => '/etc/zabbix/zabbix_agent2.d',
      'pidfile'               => '/var/run/zabbix/zabbix_agentd2.pid',
      'servicename'           => 'zabbix-agent2',
      'zabbix_package_agent'  => 'zabbix-agent2',
      'binary_location'       => '/usr/sbin/zabbix_agent2',

I actually not test with windows kernel.

This Pull Request (PR) fixes the following issues

Fixes #692

[Phil-Friderici]

Rebased against master.

[Phil-Friderici]

The spec tests all run fine when using puppetlabs/postgresql v7.5.0 instead. The latest version of postgresql introduced a bug that does fail on ArchLinux. I have create the issue#1408 with a description of the problem and @smortex was so kind (merci beaucoup!) to create PR#1410 to get it fixed.

Currently they are working on a fix and I am looking forward for a new fixed release of postgresql that should work well with this code.

Regarding the failing of the acceptance tests, I am not sure what is needed to fix them. Any help would be very appreciated.

[Phil-Friderici]

Closed in favour of #914