Ensure Stata's default log output gets written to the container's stdout

Currently we run Stata in batch mode (with the -b flag). This causes it to write it's output to a log file named <script-name>.log and means that Stata jobs have effectively zero useful information in the default logs.

We should make sure that these logs get written to stdout somehow (in a streaming fashion, not as a batch at the end, so we can see what long running jobs are up to).

It's possible that we don't actually need the -b flag but we'll have to experiment to see what the behaviour is.

Whatever happens we'll still need our wrapper script to parse the log output to try to guess whether the job has errored as Stata helpfully exits with status zero in all cases.

Start by reproducing the current Stata batch-mode invocation and inspect the wrapper script that parses log output. Experiment with the -b flag and log handling to determine how output can stream to stdout while preserving error detection. Done means long-running job output is visible in container stdout and the wrapper still parses the log output.