Trying to increase log buffer size fails miserably

... The lesson is, never try!

This is likely same / similar to the old TS-777 issue (Craig reminded me):

https://issues.apache.org/jira/browse/TS-777

I tried again with 32KB, which works fine on Docs / CI, but fails in our (much more busy) production environment. When it fails, logging stops, and we start seeing the following errors:

```
Sep 27 16:29:58 s_sys@xxx traffic_server[17236]: {0x7ffb39f0c700} NOTE: Skipping the current log entry for tcpinfo.log because its size (56) exceeds the maximum payload space in a log buffer
Sep 27 16:29:58 s_sys@xxx traffic_server[17236]: {0x7ffb3590c700} NOTE: Skipping the current log entry for tcpinfo.log because its size (56) exceeds the maximum payload space in a log buffer
Sep 27 16:29:58 s_sys@xxx traffic_server[17236]: {0x7ffb3950c700} NOTE: Skipping the current log entry for foo.log because its size (560) exceeds the maximum payload space in a log buffer
```

Note how it not only affects regular access logs, but also plugin logs (tcpinfo in this case).