[Draft] - Improve the Kedro Run log, make "go to definition" easier

[noklam]

Description

These rich logs are actually clickable, but not enough people are aware of it. It would be nice if I can jump into the definition of the function quickly from the log.

It is actually possible, but currently they are hidden in a big chunk of stacktrace and hard to discover.

In addition, these logs are not always clickable if they are too long (side-effect of rich). See #3276. Recently, #3651 also demands more concise logging.

• Rich add newline to long log message and it cannot be copy and paste directly into terminal #3276
• Better Error Logging #3651

Context

While the log is
The current stacktrace look nice, but I have to admit that 90% I either look at the last few lines in the bottom or scroll up a lot to see the Kedro log. Important information that I mentioned in the description are often missed. I am also thinking how can we make this easier combined with the %load_node feature.

Possible Implementation

Is it possible to make that important stacktrace emitted from the node function to the logs or to the bottom?

Both solution will helps a bit.

• Rich add newline to long log message and it cannot be copy and paste directly into terminal #3276
• Better Error Logging #3651

Possible Alternatives

Bad idea: Push the last ERROR/WARNING to the exception that get raised, so they will show up in the bottom.

[noklam]

https://linen-slack.kedro.org/t/16645419/does-anyone-know-why-when-i-do-catalog-load-on-a-versioned-p#48ccd9c3-adca-4104-b4b5-6427700cc2e7