Bootstrapping produces many warnings about unsupported promises

<pre>
root@cfengine-virtual-machine:~# /var/cfengine/bin/cf-agent -B 192.168.123.73
notice: Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle inventory
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle cfengine_stdlib
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle cfengine_controls
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle cfengine_reports
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle services_autorun
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle def
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle inventory_control
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle inventory_linux
Q: "...f-serverd"": warning: Trying to evaluate unsupported/obsolete promise type reports in bundle stdlib_common
R: This host assumes the role of policy server
R: Updated local policy from policy server
R: Started the server
R: Started the scheduler
notice: Bootstrap to '192.168.123.73' completed successfully!
</pre>

This is presumably because of the reports in common bundles that are only meant for reporting, however they trigger this message because DEBUG classes are evaluated after the check for which promises the particular agent/daemon supports. See for instance https://github.com/cfengine/masterfiles/blob/master/promises.cf#L265.