Implement custom DataWriter to support journeys with loading static resources

[dmlemeshko]

In order to run scalability tests with static resources been loaded, we can't use the default DataWriter.

Default one is not configurable and stores response body for each request that causes out of memory exception.

At the moment we exclude static resources from APM traces and can use existing DataWriter. But if we won't to include it, we need to consider our own implementation. There are already existing ones:

• https://github.com/gatling/gatling/blob/main/gatling-graphite/src/main/scala/io/gatling/graphite/GraphiteDataWriter.scala
• https://github.com/bmaguireibm/gatling-prometheus-datawriter
• https://github.com/Dobrynin-K/gatling-prometheus-grafana/blob/master/src/main/scala/io/gatling/prometheus/PrometheusDataWriter.scala