[8.0] Remove @kbn/legacy-logging

[mshustov]

Logging service in the legacy platform based on our fork of @hapi/good and internal logic https://github.com/elastic/kibana/blob/8e9a8a84dccfa7965ce8a22362885e6cdef8b51f/src/legacy/server/logging/log_interceptor.js

Preparation steps:

• log filtering Implement filtering mechanism in the Logging service #57547
• log rotation [KP] Implement Log rotation appender #56291
• request/response logging Log HTTP requests, responses #13241
• ops metrics data logging [logging/metrics] Provide ability to log ops data from core metrics service #86162
• make json logs ECS compliant [Core] Logs in JSON layout follow ECS format #90406
• deprecate legacy logging config Deprecate legacy logging configuration in favour of new logging system #82431
• add KP logging documentation Add user-facing docs for new logging configuration #57502

Removing legacy logging:

• Remove @kbn/legacy-logging
• Remove transformLogging logic from packages/kbn-config/src/legacy/legacy_object_to_config_adapter.ts
• Remove @hapi/good / @hapi/good-squeeze / @hapi/podium from kibana dependencies [core.logging] Remove dependency on @hapi/good, @hapi/good-squeeze, @hapi/podium #82240
• Remove legacy appender src/core/server/legacy/logging/appenders
• Remove validation that requires logging.root.appenders to have a default (this can now be optional and populated with the default value if nothing is explicitly configured) https://github.com/elastic/kibana/blob/master/src/core/server/logging/logging_config.ts#L79-L81
• Remove legacy logging mixin src/legacy/server/logging
• Update src/cli/serve/serve.js to remove references to remove deprecated flags (quiet, log-file), and remove references to deprecated legacy config (used inside verbose and silent)

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[jportner]

Regarding log rotation and retention:

We are in the planning phase for revamping Audit Logging in #52125, and we will need log rotation in place to support that. Log rotation has been added in #12259, but it only allows logs to be retained based on number of files. Industry standards generally require that organizations retain an audit trail based on a time period (e.g, 30 days, 90 days, etc.) This is currently supported in Elasticsearch, it would be great if Kibana supported this as well.

[mshustov]

@jportner there is a separate issue to migrate Log rotation #56291 you can add requirements there

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)