`outgoing_messages_bytes_limit_exceeded` takes too long to run

[ark0f]

Problem

outgoing_messages_bytes_limit_exceeded tests in pallet-gear can take up to 4 minutes to run which associated with huge memory copy

Steps

cargo test --package pallet-gear --lib tests::outgoing_messages_bytes_limit_exceeded -- --exact

Possible Solution

Use mimalloc for pallet-gear tests but test should not take so much time to run

Notes

No response

Relevant Log Output

https://github.com/gear-tech/gear/actions/runs/15727541398/job/44325541643#step:16:1521

        SLOW [> 60.000s] pallet-gear tests::outgoing_messages_bytes_limit_exceeded
        SLOW [>120.000s] pallet-gear tests::outgoing_messages_bytes_limit_exceeded
        SLOW [>180.000s] pallet-gear tests::outgoing_messages_bytes_limit_exceeded
        PASS [ 193.034s] pallet-gear tests::outgoing_messages_bytes_limit_exceeded
────────────
     Summary [ 315.545s] 965 tests run: 965 passed (1 slow), 13 skipped

[ByteNacked]

The slowdown caused by regression in scale codecs paritytech/parity-scale-codec#73 ,
will be fixed by #4779