TLSRecv now '\0'-terminates all received data.

This has been the case for the non-TLS counterpart (RecvSocketStream())
so TLSRecv() must follow the same logic to make sure all (hundreds)
callers of ReceiveTransaction() are safe.
Clarify comment.
Merge pull request #1641 from jimis/reverse_dns_access_rules

TLSRecv now '\0'-terminates all received data.
Remove some unneeded Changelog entries. They are in 3.5 already.
Redmine #5339: Fix available patches list being empty.

It happens because cf-agent -f update.cf contains a package promise
which uses an empty package_patch_list_command. The list is then
created as empty, and when cf-agent -f promises.cf comes around, the
file already exists with a recent timestamp, and therefore
regenerating it is not attempted.

Fixed by not writing the file if package_patch_list_command is empty.
Merge pull request #1642 from kacfengine/redmine5339

Redmine #5339: Fix available patches list being empty.
.gitignore: handle tests/acceptance/mock_package_manager
tests/acceptance/01_vars/02_functions/packagesmatching.cf: revise test
master becomes 3.7
Redmine#4203: test env parsing for package method
Redmine #5452: add acceptance test for maparray()
tests/acceptance/README: Add git bisect notes from @cdituri in #1317
Allow JsonParse to parse primitives at top level

Also, add JsonPrimitiveTypeToString
examples/container_iteration.cf: add useful example