[filebeat] Upgrade Kibana module to prepare for 8.0 breaking changes

The @elastic/kibana-core team has been working on [improvements to our new platform logging service](https://github.com/elastic/kibana/issues/58261) in preparation for [removing Kibana's legacy logging system](https://github.com/elastic/kibana/issues/82431) in 8.0.

As a part of these changes, the log formats have been updated to be more in line with the Elasticsearch logs which are based on [log4j 2](https://logging.apache.org/log4j/2.x/index.html). In particular, our log format for http request/response logs [has been updated to include ECS-compliant meta](https://github.com/elastic/kibana/pull/87939), and we've also [adjusted how ops metrics are logged](https://github.com/elastic/kibana/pull/88070), among other changes.

After looking at the [ingest pipeline for the Kibana module](https://github.com/elastic/beats/blob/master/filebeat/module/kibana/log/ingest/pipeline.yml), it appears that several of these referenced fields will break once the legacy logger is deprecated.

Wanted to raise this issue now so that we can discuss implications on Beats & answer any questions you might have around these changes. We have not yet removed the legacy logs from Kibana's `master` branch, but will likely do so as we get closer to the 8.0 alpha.

cc @alexh97 @kobelb