add failing p4est test

[tjhei]

This is a simple way to trigger #7428

[tjhei]

(this should of course not be merged as is)

[tjhei]

I changed the test to be expected=run, so we can merge it. @tamiko

[kronbichler]

I have one question about this test, since I see the release version failing here:
https://cdash.43-1.org/testDetails.php?test=44174832&build=6322
where failing means that the test does indeed run and not abort with an exception: Do we need the debug version of p4est here or is deal.II-debug enough? In the latter, we can append a .debug.output, but in the former I don't know immediately.

[bangerth]

It's not clear what the point of having this in the testsuite is. We still need to find the bug and a way to work around it.

[tjhei]

I have one question about this test, since I see the release version failing here:
https://cdash.43-1.org/testDetails.php?test=44174832&build=6322

The assert is only triggered in debug mode, yes. Let me make a fix.

[tjhei]

It's not clear what the point of having this in the testsuite is. We still need to find the bug and a way to work around it.

We decided to include it during our zoom meeting yesterday. Maybe merging it in the last minute was not the best idea, but generally it is good to have so that the test a) gets ported forward and b) we will know if something changes due to changes inside p4est.