Running --bug-report=rr as part of normal tests means CI might break when external packages used by it are non-functional

[KristofferC]

For example, CI now fails due to JuliaWeb/HTTP.jl#1218 (which is probably fixed soon) but still:

cmdlineargs                                      (12) \|         failed at 2025-04-09T20:58:54.061
  | Test Failed at /cache/build/tester-amdci5-13/julialang/julia-master/julia-55d9553074/share/julia/test/cmdlineargs.jl:1237
  | Expression: success(pipeline(setenv(`$(Base.julia_cmd()) --bug-report=rr-local -e 'exit()'`, "JULIA_RR_RECORD_ARGS" => "-n --nested=ignore", "_RR_TRACE_DIR" => temp_trace_dir); ))
  | Evaluated: success(setenv(`/cache/build/tester-amdci5-13/julialang/julia-master/julia-55d9553074/bin/julia -C native -J/cache/build/tester-amdci5-13/julialang/julia-master/julia-55d9553074/lib/julia/sys.so --depwarn=error --check-bounds=yes -g1 --startup-file=no --bug-report=rr-local -e 'exit()'`,["JULIA_RR_RECORD_ARGS=-n --nested=ignore", "_RR_TRACE_DIR=/cache/build/tester-amdci5-13/julialang/julia-master/tmp/jl_mgmens"]))

I think this test should be in a different category.

[DilumAluthge]

Or at least pin a manifest?