Compatibility with YADE 1.x - JumpHost CredentialStore handling

Current Situation

• When a Source/Target transfer is accessible via a Jump Host and a Credential Store is configured:
  • YADE 1.x behavior:
    • YADE requires the KeePass database file only on the host where the YADE client is installed.
    • No KeePass file is needed on the jump host.
      • The jump host YADE client is invoked using already resolved credential values.
  • YADE 2.x behavior:
    • General Rule
      • The path defined in a CredentialStoreFragment must be accessible on the system where the YADE client is executed.
    • Configuration Scenarios
      1. JumpFragment + CredentialStoreFragmentRef
         • The referenced CredentialStoreFragment must contain a path that is accessible on the local file system (YADE client host)
           • The connection to the jump host is established from the system where the current YADE client is executed.
      2. SFTPFragment (as Source/Target using JumpFragmentRef) + CredentialStoreFragmentRef
         • The referenced CredentialStoreFragment must contain a path that is accessible on the jump host
           • The connection to the Source/Target is established from the jump host where the YADE jump client is executed
    • Note: YADE client generate a temporary settings file on the jump host during execution.
      • This temporary file, deleted at the end of the transfer, contains the original Credential Store entry values, which are resolved only during the execution of the YADE Jump Host client.