TestPreconfig.test_vt_assert_no_mpi segfaults in icpx build

[cz4rs]

Reproduced on develop (9089be5) using Docker.

root@e89cb46df633:/build/vt# ctest -R TestPreconfig.test_vt_assert_no_mpi --output-on-failure
Test project /build/vt
    Start 995: vt:TestPreconfig.test_vt_assert_no_mpi
1/1 Test #995: vt:TestPreconfig.test_vt_assert_no_mpi ...***Exception: SegFault  0.06 sec
Note: Google Test filter = TestPreconfig.test_vt_assert
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from TestPreconfig
[ RUN      ] TestPreconfig.test_vt_assert


0% tests passed, 1 tests failed out of 1

Label Time Summary:
unit_test    =   0.06 sec*proc (1 test)

Total Test time (real) =   0.14 sec

The following tests FAILED:
	995 - vt:TestPreconfig.test_vt_assert_no_mpi (SEGFAULT)

First observed in #2058: see Azure logs.

I suspect that this is caused by an icpx update (we don't use pinned version in ci/docker/ubuntu-intel-oneapi-cpp.dockerfile).

root@062055a887d5:/build/vt# icpx --version
Intel(R) oneAPI DPC++/C++ Compiler 2023.0.0 (2023.0.0.20221201)

Originally posted by @cz4rs in #2058 (comment)

[cz4rs]

This keeps failing on icpc build (recent logs):

383/483 Test #383: vt:TestPreconfig.test_vt_assert_no_mpi .............................................***Exception: SegFault  0.29 sec
Note: Google Test filter = TestPreconfig.test_vt_assert
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from TestPreconfig
[ RUN      ] TestPreconfig.test_vt_assert

(...)
The following tests FAILED:
	383 - vt:TestPreconfig.test_vt_assert_no_mpi (SEGFAULT)

Either fix this or disable the test for Intel compilers if that's too much of a hassle.

[cz4rs]

DARMA weekly conclusion: disabling this test for Intel Classic is fine.