Show evaluated test arguments for functions with 1 & 2 arguments

[omus]

When using @test any function call which has 1 or 2 arguments only will always display the evaluated arguments. Having this makes it much easier at a glance to debug the problem:

julia> using Test

julia> x = [1,2];

julia> y = [1,3];

julia> @test issubset(x, y)
Test Failed at REPL[5]:1
  Expression: issubset(x, y)
   Evaluated: issubset([1, 2], [1, 3])

ERROR: There was an error during testing

Alternatively, users could use @testset let however it can be quite tedious to add those blocks to test suites.

Alternative to:

• Show evaluated test arguments for set/char/numeric comparison functions #57820

[LilithHafner]

My concern in #57820 (review) is a fair bit stronger here: sometimes the arguments might be large when printed.

[omus]

My concern in #57820 (review) is a fair bit stronger here: sometimes the arguments might be large when printed.

That is also a concern of mine. I'll look into a possible solution with displaysize yet.

Update: we're already using print with the limit context enabled so this doesn't get too crazy

[omus]

Digging into this mystery:

julia> using Test

julia> @test 1 .== 1
Error During Test at REPL[2]:1
  Test threw exception
  Expression: 1 .== 1
  UndefVarError: `.==` not defined in `Main`
  Suggestion: check for spelling errors or missing imports.
  Stacktrace:
   [1] top-level scope
     @ REPL[2]:1
   [2] macro expansion
     @ ~/Development/Julia/aarch64/latest/usr/share/julia/stdlib/v1.13/Test/src/Test.jl:705 [inlined]
ERROR: There was an error during testin

[omus]

The change required to support broadcasting is big enough that I'll make a separate PR for it. Previously, broadcasted functions never showed evaluated arguments so I'll just follow that behavior.

[omus]

CI failures look unrelated to me

[vtjnash]

SGTM, though I don't see why there is a restriction on being a "simple call", when the printing logic doesn't care about that