Pgbelt should output which database and environment a stack trace is thrown for!

[vjeeva]

Is your feature request related to a problem? Please describe.
In #87, it took the team a while to realize which database was throwing the timeout errors. The stack trace said there was a statement timeout, but not for which database and environment. The logger printed a bunch of stuff and each thread prints to it asynchronously in different orders so the last line before the stack trace wouldn't necessarily be the database that had the error.

Describe the solution you'd like
When a stack trace is thrown, make it clear in the terminal output that it was thrown for X database in Y environment.

Describe alternatives you've considered
No solution would make diagnoses like the above take longer than preferred.

[vjeeva]

https://github.com/Autodesk/pgbelt/blob/main/pgbelt/cmd/sync.py#L45-L52 Like there, catch and show which thread or pool had the issue?