Motivation:

- the actual command we run is pretty meaningless without context.
- to provide the context, we would need to add additional 'logging.info' command
  BEFORE we call `run`
- if we select loglevel `debug` we get to see the same output as before.

Print log

See merge request mpsd-cs/mpsd-software-environments!30

Logfile records everything, but logging output to screen can be adjusted

See merge request mpsd-cs/mpsd-software-environments!31

if MPSD_MICROARCH is not defined, use archspec to determine

See merge request mpsd-cs/mpsd-software-environments!32

Output to the shell is adjusted using the loglevel argument.

- full date is in file name
- can just use the time in here (could also remove that)

improve machine readable logging

Closes #6

See merge request mpsd-cs/mpsd-software-environments!28

Merge branch 'improve-machine-readable-logging' of gitlab.gwdg.de:mpsd-cs/mpsd-software-environments into improve-machine-readable-logging

Use logging.error (nice red display with rich) and hide exception

See merge request mpsd-cs/mpsd-software-environments!25

Revert "Merge branch 'complete-tests-for-run' into 'main'"

See merge request mpsd-cs/mpsd-software-environments!26

This reverts merge request !21

test that the counter works

See merge request mpsd-cs/mpsd-software-environments!21

use rich for logging formatting (if package available)

See merge request mpsd-cs/mpsd-software-environments!23

Simplify implementation of rich

See merge request mpsd-cs/mpsd-software-environments!24

- sys.__stdout__ is the value stdout had at the beginning of the Python program.
- instead, let's reconnect to the stdout stream we used immediately before we
  redirected into the StringIO object. This should be (mildly) more robust.