Compatibility with YADE 1.x - JumpHost CLI argument transactional handling

Current Situation

• The JumpFragment / YADEClientCommand can be configured using an additional boolean transactional argument, e.g.:

  YADEClientCommand=/<...>/yade.sh -transactional=false

• This JumpHost YADE CLI argument controls the transactional mechanism performed by the YADE client on the JumpHost.
• YADE 1.x
  • The reason for introducing this argument is described in YADE-608: ... In some situations (e.g. when the rename operation is not allowed), the YADE4DMZ transfer fails.
• YADE 2.x
  • The reason example mentioned above is no longer relevant, because YADE 2.x does not require an atomic transfer for transactions when no atomic option is explicitly defined.
    • Each transfer is performed in its own temporary directory on the JumpHost, so an atomic rename is not needed.
      • Avoiding the additional rename also speeds up the transfer.
  • However, transactional means more than just an atomic rename.
  • Therefore, the switch should remain available, but currently it has no effect.

Desired Behaviour

• The transactional switch of YADEClientCommand should work as expected.

Test Instructions

• Test JumpHost functionality with TransferOption / Transactional set to true and false.
• Test with YADEClientCommand without and with the transactional argument.
• The JumpHost YADE client logs should show the corresponding Transactional value.