feat: Correct top-level calls are shown for the vast majority of errors

[krlmlr]

Also call abort() directly, avoid handling condition objects.

This PR uses my_caller_env() from c147ebf to automatically retrieve the calling environment for correct error locations. Is there any downside, compared to the recommended approach of passing caller_env() across the entire chain of calls?

[lionel-]

This PR uses my_caller_env() from c147ebf to automatically retrieve the calling environment for correct error locations.

🙀

[krlmlr]

What levels of horror is your 🙀 cat experiencing?

[lionel-]

It's a moderate level of horror. I don't know if this scheme could fail in this case, but I would expect tibble to be exemplary, given its place in the tidyverse, and use the conventional call = caller_env() passing pattern that we use in other packages and which is clearly correct in first analysis.

If it's very costly to add these arguments, then I'd prefer to see some global state peeking/poking, possibly laid out in a stack (e.g. using the call stack via on.exit() restoration of global values) if there is any possibility of recursing into a new instance of tibble code (is there?).

[krlmlr]

Thanks. I don't believe we ever recurse. For now I'll add a comment that this is an anti-pattern, I'll deal with it as part of the frontend-backend separation.