Implement stream similar messages for VSI-Server

[ReinhardKeil]

See: #136

Suggestion is that the VSI-Server should also print messages about the Stream input/output to the console.

Stream input:  DataInput (DataInput.0.sds).
Stream output: DataOutput (DataOutput.2.sds).
...........
Stream closed: DataInput (DataInput.0.sds).
Stream closed: DataOutput (DataOutput.2.sds).
Stream input:  DataInput (DataInput.1.sds).
.
Stream output: DataOutput (DataOutput.3.sds).

Current output does not show which files are used. Example:

 *  Executing task: FVP_Corstone_SSE-300 -f Board/Corstone-300/fvp_config.txt -a out\AlgorithmTest\AVH-SSE-300\DebugPlay\AlgorithmTest.axf  

100% idle
100% idle
SDS playback and recording started
Predictions (DSP: 3.000000 ms., Classification: 0 ms., Anomaly: 0ms.): 
#Classification results:
    idle: 0.000000
    snake: 0.000000
    updown: 0.011719
    wave: 0.988281
Anomaly prediction: -0.334040
Predictions (DSP: 3.000000 ms., Classification: 0 ms., Anomaly: 0ms.): 
#Classification results:
    idle: 0.000000
    snake: 0.000000
    updown: 0.015625
    wave: 0.984375
Anomaly prediction: -0.325139
Predictions (DSP: 3.000000 ms., Classification: 0 ms., Anomaly: 0ms.): 
#Classification results:
    idle: 0.000000
    snake: 0.000000
    updown: 0.085938
    wave: 0.914062
Anomaly prediction: -0.009358
Predictions (DSP: 3.000000 ms., Classification: 0 ms., Anomaly: 0ms.): 
#Classification results:
    idle: 0.000000
    snake: 0.003906
    updown: 0.011719
    wave: 0.984375
Anomaly prediction: -0.075508
SDS playback and recording stopped
92% idle
100% idle
100% idle
100% idle
100% idle
100% idle
100% idle
100% idle
99% idle
100% idle
100% idle
100% idle
100% idle
```

[ReinhardKeil]

@DavidLesnjak Maybe it is better to create a log file, i.e. sdsio.log where these messages are recorded. In this way, I could see what the simulation did execute.

So effectively two files that are used by sdsio-vsi:

sdsio.yml - configuration setting (read)
sdsio.log - process output (similar to sdsio-server)

[DavidLesnjak]

Agreed on using sdsio.log. I suggest aligning the messaging with SDSIO-Server.py for consistency, but dropping the progress-dot bar—it adds complexity with little benefit, since the output is written to a file and isn’t visible during execution.

[MiloradCvjetkovic]

I'd suggest a bit more descriptive file names:
for example:

• sdsio.yml -> sdsio_config.yml
• sdsio.log -> sdsio_fvp.log