Better Error UX

[appetrosyan]

2022-07-07 11:09:49.711  INFO 781 --- [    Test worker] 🐳 [hyperledger/iroha2:stable]           : Container hyperledger/iroha2:stable is starting: 9da2dc9f26de6590df44157b6f76d0a4b32b77e8deb616495663940b5713f0fd
2022-07-07 11:09:49.752  INFO 781 --- [ream-1662371293] j.c.s.i.testcontainers.IrohaContainer    : STDERR: thread 'main' panicked at 'OS can't spawn worker thread: Operation not permitted (os error 1)', /cargo_home/registry/src/https-1xa.pages.dev-1ecc6299db9ec823/tokio-1.18.2/src/runtime/blocking/pool.rs:264:29
2022-07-07 11:09:49.753  INFO 781 --- [ream-1662371293] j.c.s.i.testcontainers.IrohaContainer    : STDERR: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2022-07-07 11:09:49.751  INFO 781 --- [    Test worker] o.t.c.wait.strategy.HttpWaitStrategy     : /optimistic_kepler: Waiting for 60 seconds for URL: http://172.17.0.1:32775/status (where port 32775 maps to container port 8180)
2022-07-07 11:10:49.795 ERROR 781 --- [    Test worker] 🐳 [hyperledger/iroha2:stable]           : Could not start container

is an example of a traceback that doesn't explain what went wrong, and the user is left guessing if this is even a configuration error or if Iroha cannot spawn at all, due to a conflict with the OS or permissions.

Printing the error traceback in such a case would be useful.