Fix OOM test for HOST ALL memspace

[kswiecicki]

Adjust alloc size to 4MB. Add an access to each allocation so that pages are actually allocated on the selected NUMA nodes.

Fixes: #285

This also fixes the nightly workflow fails here: https://github.com/oneapi-src/unified-memory-framework/actions/runs/8148821384.
Nightly workflow run with these changes on my fork: https://github.com/kswiecicki/unified-memory-framework/actions/runs/8188227540.

[ldorau]

@kswiecicki CI build fail

[ldorau]

@kswiecicki #285 is already fixed by #295

[lukaszstolarczuk]

@kswiecicki, I can see you're doing some changes yet - is it ready to review/merge at this moment? 😉 if you still testing this, consider changing this PR to draft, please.

[ldorau]

The Nightly build with your PR fails: https://github.com/ldorau/unified-memory-framework/actions/runs/8169938615/job/22335017162

[kswiecicki]

The Nightly build with your PR fails: https://github.com/ldorau/unified-memory-framework/actions/runs/8169938615/job/22335017162

After talking to @igchor and discovered that provider_os_memory_config tests had similar problems with memory policy assertions under valgrind. For that reason I've added a similar suppression for memspace_host_all test. Nightly tests shouldn't fail now.

[kswiecicki]

I've rewritten the test case according to what we came up with on standup @bratpiorka. It seems that OOM killer no longer kills it. The test also worked correctly on a platform with 2 numa nodes with #ifdef 0 removed.

Also, I've added a skip for this test case if it was built with TSan, because it exits with 143 error code without providing any further info.

[ldorau]

Valgrind memcheck build PASSes: https://github.com/ldorau/unified-memory-framework/actions/runs/8188719802