feat: check tty / jupyter availability for logging config detection

[wochinge]

Related Issues

• related to Introduce structured logging #7027

Proposed Changes:

• be a bit smarter than before and automatically switch to JSON logging if there is no tty (following the recipe from here: https://www.structlog.org/en/stable/logging-best-practices.html#pretty-printing-vs-structured-output and adapting it to Jupyter)
• above behavior is of course disablable

How did you test it?

Notes for the reviewer

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 8067647306

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.1%) to 90.07%

---

Files with Coverage Reduction	New Missed Lines	%
logging.py	1	97.96%

Totals
Change from base Build 8066845210:	0.1%
Covered Lines:	5270
Relevant Lines:	5851

---

💛 - Coveralls