InteractiveUtils test sometimes causes CI failure

[LilithHafner]

Recent CI failure

Error in testset InteractiveUtils:
--
  | Test Failed at /cache/build/tester-amdci4-13/julialang/julia-master/julia-234a7586c3/share/julia/stdlib/v1.11/InteractiveUtils/test/runtests.jl:232
  | Expression: #= /cache/build/tester-amdci4-13/julialang/julia-master/julia-234a7586c3/share/julia/stdlib/v1.11/InteractiveUtils/test/runtests.jl:232 =# @allocated(varinfo(Tmp14173)) < if MEMDEBUG
  | 300000
  | else
  | 100000
  | end
  | Evaluated: 100352 < 100000

Test added in #36107 cc @vtjnash

Fails intermittently and only on x86_64-linux-gnuassertrr

[vtjnash]

I thought I just increased the allowable allocs there, but anyways, we should just increase it by 50% again

[Zentrik]

This test behaves in a weird way as the reported number of allocations seems to depends on whether the test uses a < or a ==.

[LilithHafner]

If the response to a test failure is to increase the limit, should we just remove the limit?

[vtjnash]

The limit is to measure that it is not significantly unbounded memory relative to the thing it is measuring. As the measured thing grows, sometimes we need to increase the test