Network remappers should also handle `host.network.*` metrics

Current network remappers only produce `system.network.*` metrics, however, curated UIs also require `host.network.*` metrics ([ref](https://github.com/elastic/kibana/blob/a9cb7d2423f135214b2c6df945b667296cb75176/x-pack/plugins/observability_solution/infra/server/routes/overview/lib/create_top_nodes_query.ts#L27-L196)). We should produce both of these metrics in the remappers.

As per ECS, there are 4 `host.network` metrics that needs to be produced:

1. [host.network.egress.bytes](https://www.elastic.co/guide/en/ecs/current/ecs-host.html#field-host-network-egress-bytes)
2. [host.network.egress.packets](https://www.elastic.co/guide/en/ecs/current/ecs-host.html#field-host-network-egress-packets)
3. [host.network.ingress.bytes](https://www.elastic.co/guide/en/ecs/current/ecs-host.html#field-host-network-ingress-bytes)
4. [host.network.ingress.packets](https://www.elastic.co/guide/en/ecs/current/ecs-host.html#field-host-network-ingress-packets)

Unlike `system.network.*` metric, the `host.network.*` metrics seems to be an aggregate over all network devices and are gauges.