Static tasks may wakeup in wrong order after all Tasks have called rX_SysSetTaskInitialized (lasts until next scheduler call)

The wakeup order of static tasks after the synchronisation barrier may be wrong due to a missing scheduler operation at the end of the rX_SysSetTaskInitialized() function.
As long as the timer interrupt is pending during the static task wakeup operation, the wakup order of the tasks will be correct. In any other case the task which triggers the wake-up will be the first which (illegaly) passes the synchronisation barrier. Nevertheless the wakup order is fixed subsequently with the schedule operation of the next kernel tick. See attached test case for further investigation!