[Argus] use ES data streams, enable log correlation

[kdembler]

• Changed Argus Elasticsearch transport to use data streams instead of regular indices. Renamed config.logs.elastic.index to config.logs.elastic.indexPrefix. Node ID from config will be automatically appended to the index name.
• Changed Colossus Elasticsearch transport to use data streams instead of regular indices. Removed --elasticSearchIndex option and replaced with --elasticSearchIndexPrefix. Node ID from config will be automatically appended to the index name.
• Updated example distributor node config to match values currently used in production.

[kdembler]

@zeeshanakram3 FYI, did the same for Colossus as well

[zeeshanakram3]

As the integration-test logs suggest that the colossus-1 is not serving any buckets (i.e. storage node during initialization could not find worker/buckets that it's supposed to serve). I think this is mainly because QN is lagging and info about worker/buckets created in the previous step hasn't been processed yet.

Fix

Add sleep after completion of initStorageAndDistribution scenario to give time to QN for blocks processing