Initial support to load rules from a remote server

New directive `SecRemoteRules' was added. It allows the user to load a
set of rules from a given HTTP server.
Adds the SecRemoteRulesFailAction directive

This directive allows the user to set a default action whenever the
SecRemoteRules failed to download a set of rules. Current the supported
values are: Warn and Abort. By default `Abort' is selected.
Adds SecRemoteRules as an build option

SecRemoteRules adds a new dependency to libcurl. Before only mlogc was
depending on libcurl. SecRemoteRules also depends on the apr-tools with
crypto support, which (as reported by our buildbots) is not default in
some environments such as: MacOS X. This commit disable SecRemoteRules
support if apr-tools was not compiled with crypto support.
Adds the `crypto' option to SecRemoteRules directive

Originally the SecRemoteRules fetch the rules from an remote server in an
specific format, using cryptography. This patch adds the possibility to
load rules in plain/text format.
Forces downloads using https-only for resources or rules

This commit makes ModSecurity to refuse to download or install rules
(SecRemoteRules) from sites that are not running HTTPS with a valid and
trusted certificate.
Adds SecRemoteRules regression tests.

Added two test cases for SecRemoteRules. Contents are loaded from
https://www.modsecurity.org
Adds regression test for FILE_TMP_CONTENT
Build: New alternative to identify the presence of libfuzzy

Searching for the fuzzy.h instead of the .so file.