Disables response logging as a default (#42353)

Previously, if any of the following were true, we would log HTTP responses.
- `logging.json` was set
- `logging.dest` was set
- `TTY` was detected

The logging format should not dictate what is logged

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>

docs/migration/migrate_8_0.asciidoc

@@ -48,6 +48,12 @@ for example, `logstash-*`.
 
 *Impact:* To restore the previous behavior, in kibana.yml set `logging.timezone: UTC`.
 
+[float]
+==== Responses are never logged by default
+*Details:* Previously responses would be logged if either `logging.json` was true, `logging.dest` was specified, or a `TTY` was detected.
+
+*Impact:* To restore the previous behavior, in kibana.yml set `logging.events.response=*`.
+
 [float]
 ==== `xpack.security.authProviders` is no longer valid
 *Details:* The deprecated `xpack.security.authProviders` setting in the `kibana.yml` file has been removed.

src/legacy/server/logging/configuration.js

@@ -45,7 +45,6 @@ export default function loggingConfiguration(config) {
   else {
     _.defaults(events, {
       log: ['info', 'warning', 'error', 'fatal'],
-      response: config.get('logging.json') ? '*' : '!',
       request: ['info', 'warning', 'error', 'fatal'],
       error: '*'
     });