Feat: Allow disabling rich tracebacks via env var

[fg91]

TL;DR

In flytekit==1.6.0 rich tracebacks were introduced (#1582).

Before, exceptions were shown like this:

After, they are shown like this:

This happens as long as import flytekit is called somewhere in the imported code base, also when not directly working with flyte.

---

Style ultimately is a question of taste but several of our engineers have complained about this change:

When/Why did the stacktrace get so ugly colorful. It takes up way too much space and pycharm cannot create crosslinks to the files anymore for me 🙈 And long lines are truncated

I feel the same, does not help me

Can we configure this

I wanted to complain about this too 😄

The tracebacks contain way more (white space) characters, meaning I can paste a lot less of them into chat gpt

Because of this, in this PR I propose to introduce an environment variable which disables rich tracebacks. I chose a naming inspired by "FLYTE_SDK_LOGGING_LEVEL" or "FLYTE_SDK_LOGGING_FORMAT" in flytekit/loggers.py.

Would this change be be acceptable to you @cosmicBboy @kumare3 @eapolinario ?

Type

• Bug Fix
• Feature
• Plugin

Are all requirements met?

• Code completed
• Smoke tested
• Unit tests added
• Code documentation added
• Any pending items have an associated Issue

Complete description

NA

Tracking Issue

NA

Follow-up issue

NA

[kumare3]

I like the idea, just find the bar name too big. Want to start making smaller feature flags

[fg91]

I like the idea, just find the bar name too big. Want to start making smaller feature flags

What do you think about FLYTE_RICH_TRC or FLYTE_RICH_TRACE instead of FLYTE_SDK_RICH_TRACEBACKS?

[eapolinario]

I'm ok with more descriptive environment variables if their use is restricted (which is the case of this PR).