BS-2649, fix migration of catch event

Root cause: parentProcessId was not sed on catch event in 6.0.2 and message_instance were not deleted after handled

Changes: set the parentProcessId to rootProcessId + delete all message_instance already handled