manpage: ensure a maximum width for the text version

[bagder]

... using the new script 'maxline' to which we specify the maximum number of columns we allow any single line to be, or it will cause an error.

Bonus: shorten the long line in the --ipfs-gateway section.

[jan2000]

So, I was already wondering about the line limit yesterday, because I have this long line in PR #14407:

For OpenSSL, wolfSSL, mbedTLS, Secure Transport and BearSSL a valid example
of a cipher list is:
**ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305**

(Which I really want to keep this way because these four ciphers are the equivalent of the two ciphers in the TLS1.3 example.)

What to do with this then?

[bagder]

Either we come up with a shorter example, or we figure out a way how to split it into multiple lines.

[bagder]

Also, the current limit is set to 100 columns but that's a bit arbitrary. We can tweak it if we think we should.

The most important thing is that code in src/tool_help.c has an array size that is larger than the longest line, so I want this to make sure this is true.

[dfandrich]

Analysis of PR #14423:

Test 1026 failed,
which has NOT been flaky recently,
so there could be a real issue in the PR.
Note that this test has failed in 6
different CI jobs (the link just goes to one of them).

Test 216 failed,
which has NOT been flaky recently,
so there could be a real issue in the PR.
Note that this CI job has had a number of other flaky tests recently
(2, to be exact) so it may be that this failure
is rather a systemic issue with this job and not with this specific PR.

Test 340 failed,
which has NOT been flaky recently,
so there could be a real issue in the PR.

Test 165 failed,
but it has been permanently failing lately,
so it's probably NOT a fault of the PR.

Generated by Testclutch