[NonInterruptiveEvent]: being able to have a default value for the parameter PHASED.TESTS.PHASE

### Expected Behaviour
Currently we have different way to execute different combination of testing with even, but the -DPHASED.TESTS.PHASE parameter is mandatory to being able to execute non interrutive event.

For exemple we can have for now the mode 23 (-DPHASED.TESTS.PHASE='NON_INTERRUPTIVE(23)') to be sure that
the event is finished before calling the test method.

We have also the mode 33 (-DPHASED.TESTS.PHASE='NON_INTERRUPTIVE(33)') to call in the same time the event and the test
method to allow a completely different scenarion.

### Improvement request

We need probably to have a default mode, to being able to trigger test method with even without this parameter.

I think the NON_INTERRUPTIVE(23) should be a good candidate for a default mode, given it's in this mode we have better chance
to reproduce the same exactly STR in case of reexecution of test.

Start by tracing how the PHASED.TESTS.PHASE parameter is read and how NON_INTERRUPTIVE modes 23 and 33 affect event and test-method execution. Verify the behavior when the parameter is absent, while preserving explicit mode selection; done means a default mode works without the parameter and the existing modes still behave as described.

Written by the indexing model from the issue text.