In case an alternative connection is used then alternative_* parameters for source/target directory and post_/pre_commands are used too

Current Situation
In case an alternative connection is used then the following parameters are ignored:

• alternative(source|target)dir
• alternative(source|target)pre_transfer_commands
• alternative(source|target)post_transfer_commands
• alternative(source|target)pre_command
• alternative(source|target)post_command
• alternative(source|target)post_tfn_command

Instead, the parameters without the prefix alternative_ are used:

• (source|target)_dir
• (source|target)_pre_transfer_commands
• (source|target)_post_transfer_commands
• (source|target)_pre_command
• (source|target)_post_command
• (source|target)_post_tfn_command

For example if the source directory from source_dir doesn't exist on the alternative source host then JADE ends with an error.

[copy_with_alternatives]
operation = copy
source_host = mySourceHost
source_port = 22
source_protocol = sftp
source_ssh_auth_method = password
source_password = xyz1
source_user = test1
source_dir = /home/test1/data
alternative_source_host = myAlternativeSourceHost
alternative_source_port = 21
alternative_source_protocol = ftp
alternative_source_passive_mode = true
alternative_source_password = test2
alternative_source_user = xyz2
alternative_source_dir = /home/test2/data
recursive = true
file_spec = \.txt$
target_host = myTargetHost
target_port = 22
target_protocol = sftp
target_ssh_auth_method = password
target_password = xyz3
target_user = test3
target_dir = /home/test3/data

Desired Behavior
In case an alternative connection is used then the source resp. target parameters are ignored and only the alternative_* parameters are used