parsing of signature algorithm and key size

add parsing of signature algorithm and key size from the individual
results, report summary
report number of servers that use ECDSA and RSA certificates

Since use of both ECDSA and RSA certificates is easy, it is
relatively simple to support both. Report the total number of
such servers
add ability to ignore results from untrusted servers
in "no-untrusted mode": filter out ADH and AECDH suites

If server negotiates ADH or AECDH suite, openssl returns "ok" in
cert checking. Don't mark server as trusted because of that.

Don't collect statistics on servers that provide only untrusted
connections.
fix spelling in TLS stats (TLS1_1 vs TLS1.1)
fix and extend reporting of AES-GCM ciphers

AES-GCM ciphers don't have "AES-GCM" substring in the openssl name

extend reporting of AES ciphers, split to AES-CBC, AES-GCM and
AES in general
add support for Chacha20 based ciphers

Basically all Google servers support Chacha20 now and it is
not a bad choice, so report it as a regular cipher
fix reporting of the TLS1.2 but not TLS1.1

Some servers may be configured to support only TLS1.2, it would
count them towards the number of servers affected by the OpenSSL bug
more detailed PFS report

Just because server supports some bad DH params, doesn't mean
it will force them on users. Report number of servers
that prefer specific DH params.
extend SSL stats

Two interesting server configurations are ones that support
only SSL3 or TLS1 only (old, but otherwise correctly configured servers)
and ones that support only TLS1.1 or up (brave admins that support
only new clients)
extend reporting of RC4-related stats

While preferring RC4 in TLS1.0 or SSL3 was recommended before,
it was always known that TLS1.1 and TLS1.2 were not vulnerable against
BEAST, so forcing RC4 there is a mistake. Report number of such servers.
Merge pull request #15 from tomato42/reporting-improvements-03

Reporting improvements 03