YADE Pre/Post Processing - custom ProcessingCommandDelimiter is ignored

Current Situation

• YADE supports Pre/Post Processing to execute commands if command execution is allowed by the respective provider.
• Multiple commands can be defined;
  • they are split according to ProcessingCommandDelimiter (default:  ;  ) and executed individually.
• However, setting a custom ProcessingCommandDelimiter is ignored, and the default ; is always used.

Desired Behaviour

• Setting a custom ProcessingCommandDelimiter should work as expected, allowing commands to be correctly split and executed according to the user-defined delimiter.

Patch

• Use the cumulative patch provided with YADE-632

Test Instructions

• Test with all providers that allow Pre/Post Processing (Profiles/.../..FragmentRef/...).
  • Define multiple commands using the default delimiter, e.g., echo 1;echo 2
    • Expected result: 2 commands are executed individually.
  • Change ProcessingCommandDelimiter to a custom value, e.g., MYDELIMITER.
    • Command not changed: echo 1;echo 2 (does not contain MYDELIMITER).
      • Expected Result: treated as 1 command because the custom delimiter isn't present.
    • Command changed: echo 1MYDELIMITERecho 2
      • Expected Result: 2 commands executed individually, split by MYDELIMITER.
• Additionally, check JumpFragment/SFTPProcessing/ProcessingCommandDelimiter.