Mustache: acceptance test for default case and extra debugging
Redmine#3611: abortclasses should trigger from a common bundle too
Unit test for concurrent access to local storage (supports TC and LMDB)
Redmine#3781: acceptance test for namespaced edit_line bundle
A files promise with no action now prints a message.
Deprecate logging contexts to local database
Add string set serialization test
Remove leftover comment.
(cherry picked from commit f957351e725c347bbacb39f7e552625f6f5c6235)
Fix cf-serverd not reloading policies when they have changed.

The root of the problem was that the code to check for updated
promises was shared between cf-agent/cf-promises and the daemons, but
they have different semantics. cf-agent/cf-promises need to check
whether any files have changed so they can update
cf_promises_validated. To do this, a check that compares
cf_promises_validated to each file in inputs is needed, which is what
the existing code is doing.

The daemons however, need to compare the modification time of
cf_promises_validated against the time that they last reloaded the
policies, which is a value that should be kept in memory.

This was fixed by running a simple stat in the daemons and comparing
that to the time of the last seen cf_promises_validated. Also made
sure that cf-agent is the only one updating the cf_promises_validated
file. It's not the daemons' responsibility to do this.

Redmine #3809.
(forward-ported from commit 19c790c1f11eda9b84ced6bc09569e02b7958024
in 3.5.x.)

Conflicts:

	cf-execd/cf-execd.c
	cf-serverd/cf-serverd-functions.c
	cf-serverd/cf-serverd-functions.h
	libpromises/generic_agent.c
	libpromises/generic_agent.h
Merge pull request #1176 from tzz/master

Redmine#3283: add group=Network tag to network-related classes and varia...
Move TimeAbs2Int to the place of use
Move Months2Seconds to the place of use
Move Day2Number to the place of use
Remove unused global variable
Remove unused CFINITSTARTTIME and associated code
Move CFLOCK to the place where it is used
Move CF_LOCKHORIZON to the place of use
Remove unreachable trust-checking code and associated machinery

There used to be a time when cf-serverd checked IP reported by the
client and did some trust calculations based on that (including
denying connections from NATed hosts, because NATed hosts didn't
know their IP address as it is seen from cf-serverd side).

In order to overcome NAT issue "skipverify" option has been introduced, to
exclude some IPs/networks from IP/DNS lookup checks.

In CFEngine 3.0 this code became unreachable and stayed like this until today,
and nobody noticed. Hence, it's safe to remove it and deprecate "skipverify"
option.
Merge pull request #1158 from dottedmag/cleanup/remove-server-connection-state-trust

Remove unreachable trust-checking code and associated machinery
Force cf-agent to be the only one to write cf_promises_validated.

This is so that the separation is clear: cf-agent writes the file, the
daemons read the file.