Add option to turn off emojis in exceptions

[kubukoz]

The flood of 🔥 emojis looks cool and definitely draws attention when you hit an issue in local development, but it's not well supported in all CI systems, and certainly not in all logging systems. There should be a way to tweak this behavior, perhaps even with sane defaults such as disabling the fires when CI=1 or based on some terminal variables.

[kubukoz]

In addition, although emojis work in apps like DataDog, the ANSI escape codes don't - these should probably be conditionally stripped as well.

[mpilquist]

Some things to consider on this one:

• should this be configured globally (e.g. via environment variable or system property) or via session level configuration parameter (e.g. Session.Builder[F].withPrettyInfo(false)...)
• emojis and ANSI escapes are used pervasively throughout the code base in both exceptions and debug statements - should the enablement/disablement be communicated to all places strings are constructed? Or should strings get constructed as-is and then stripped/scrubbed before printing?

[Zijie000]

I’m inclined towards the session-level + boundary scrubbing approach, mainly because this seems to be a presentation concern rather than something affecting core behavior.
Given how widely emojis and ANSI escapes are used, propagating configuration through all construction sites might lead to fairly invasive changes. A boundary-based solution might offer a more contained way to address the issue.