put tls cipher info into Received header according to rfc8314

[celesteking]

Instead of inscribing TLS cipher info into comment like it's done now, follow this new RFC instead and put it into tls clause. This will probably require:

• grooming ciphersuite names from openssl's format into IANA's if nodejs doesn't support it by other means.

Before: (cipher=ECDHE-RSA-AES256-GCM-SHA384)
After: tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 . (not sure if dh group could possibly be ever extracted)

[Juerd]

Node.js from v12.16 and v13.4 support cipher.standardName in addition to cipher.name to get the IANA formatted cipher name. Since Haraka already specifies >= 12.20.1, it is already available.

I think adhering to the RFC is a good idea, even if this means we lose the additional information that Haraka does now log (TLS version and whether (client?) verification succeeded). The additional information, including the embedded value of authheader does not seem to be compliant along the Stamp EBNF in RFC 5321 section 4.4; maybe this is a good opportunity to remove that as well. I'm not sure about envelope-from which is formatted like an additional clause but I can't find whether it's actually registered.

[msimerson]

I was planning to lower the min node version back to 10 as we have resolved the issue requiring the bump. It would be nice if a PR implementing this is added progressively.