Remove SELinux-related bundles
Add: Local user inventory module

The local user inventory module parses and reports local user
information as discovered in /etc/passwd and /etc/shadow. Additional
bundles are provided to augment the Mission Portal Inventory UI with
interesting information such as users with locked accounts, when users
last changed their password, and users that have empty passwords.

Ref: https://dev.cfengine.com/issues/6213
Change: Inventory date of last password change report as epoch

Instead of trying to localize the time format on the client, report in
epoch format so that we can build filters and conditions based on a
standard time format.
reduce the amount of monitoring probes down to 33% or less to save hub reporting load
Add daemonize bundle
Packahge method pip needs to use pip_knowledge
Switch to autotools to avoid maintaining ugly Makefile platform hacks.

The existing approach does not work on AIX (and possibly others).
Fix tests on esoteric platforms where gmake is a better choice.
Merge pull request #281 from estenberg/limit-ootb-monitoring

reduce the amount of monitoring probes down to 33% or less
Disable package tests on platforms the tests haven't been adapted to.
Change: Cleanup inline docs
Merge pull request #287 from nickanderson/daemonize

Daemonize
Merge pull request #277 from nickanderson/redmine/6213

Add: Local user inventory module
Merge pull request #284 from bahamat/fix_package_method_pip

Packahge method pip needs to use pip_knowledge
Merge pull request #271 from phnakarin/fix#5558

Redmine#5558: Remove SELinux-related bundles
Revert "Add: Local user inventory module"
Change: Specify 'Unsupported' for dmidecode strings on rhel4

Ref: https://dev.cfengine.com/issues/630

Old versions of dmidecode do not provide a good way of extracting
strings.
Merge pull request #288 from cfengine/revert-277-redmine/6213

Revert "Add: Local user inventory module"
Fixed systemctl paths reference in services.cf
Move reading of cf-consumer.pid to def.cf and guard it by enterprise and hub classes.

Redmine: 6303

This is necessary because class guards do not protect function evaluation when calling methods.

eg.

bundle1
  methods:
  class1::
   usebundle => bundle2;

bundle2
  methods:
  # class1 needs to be used here as well
  # Otherwise cf-promises will try to read the file
  # In our case, this file doesn't exist in client nodes
  class1::
    "data" string => readfile(...);