[#148 Implement TES Task Runner] Improve node execution stdout and stderr publishing

[giventocode]

Problem:
Stdout/stderr files are only accessible after the task is finished. This makes it hard to troubleshoot long running tasks. Batch uploads these files using SAS tokens that the TES server generates beforehand. In Terra, these tokens might expire if the workflows take too long to execute

Solution:
Publish stdout and stderr data to Azure storage as they are being produced by the runner.

AC:

• Create separate files for each operation: download-stdout.txt, execution-stdout.txt, upload-stdout.txt, download-stderr.txt, execution-stderr.txt, and upload-stderr.txt.
• Use append blobs and be aware of their limits (4 MiB per block and 50,000 blocks maximum).
• Upload operations must be asynchronous and not blocking.
• The TES server must set the location of the logs and the transformation strategy to obtain the JIT SAS token.
• Improve log format - the current md format is hard to read.