Find a way to better manage Disposable(Array Pool List) Entities.

[obasekiosa]

Description
This is more of a ux/optimazation issue.

Right now Disposable (Array Pool List) entities in the code base are disposed/handled based on the discretion of the dev.
It is very easy to forget or mishandle a disposable object(entity), either by multiple dispose, or forgetting to dispose without any feedback/warning.
Its basically left to the user to be careful in memory management, especially for cases of nested calls, creation of managed memory deep within the call stack but returned, made use of and disposed at a much higher point in the stack.

Disposable objects, make use of memory pools which need to be returned to the pool after usage.
The difficulty is knowing when to return, especially if the object is created and then passed(owned) by a different object.
This behavior is quite similar to rusts idea of ownership and memory management.

Maybe there's a solution along those lines ?

Actual behavior
Running all Nethermind tests locally and in parallel seems to cause

Exit code is 134 (Unhandled exception. System.InvalidOperationException: ArrayPoolList hasn't been disposed. Created    at Nethermind.Core.Collections...

Expected behavior
ArrayPools should be easier to properly disposed/managed.
Hence making it simpler to spot cases where the above error might happen or impossible to happen?

[emlautarom1]

This has been an issue for some time now. See:

• Test suite fails when not using release config #7285
• Dispose pooled messages after sending #7186

The current workaround is to run the full test suite in Release config like we do on CI.