For stack traces, there is a function print_type_stacktrace which handles the colour printing of types. Overloading that to shorten things doesn’t seem likely to break anything else, and might be worth doing in general. Also discussed a bit in this thread. (Edit – maybe this is the issue: https://github.com/JuliaLang/julia/issues/36517 .)
I don’t think that would affect method error printing. It would be nice if that could be abbreviated to enough levels to show the mismatch, somehow. If f only accepts some particular kind of AbstractArray, and I call it with a tuple (of complicated objects), then the mismatch is at the outermost layer.