Provide Separate CheckSize Configuration for Intermediate Jump Host Transfer

Current Situation

In YADE 2.x, a file transfer through a Jump Host consists of two transfer steps: Source → Jump Host → Target. The existing CheckSize configuration controls the file-size validation of the transfer to the final Target, while the intermediate Source → Jump Host transfer is handled separately and does not currently provide an independent configuration option for its file-size validation.
As a result, customers cannot independently control whether file-size validation should be performed for the intermediate transfer.

Desired Behavior:

A separate configuration option should be provided to control file-size validation for the intermediate Source → Jump Host transfer. This option should allow CheckSize to be enabled or disabled independently for the intermediate transfer without affecting the CheckSize behavior of the final Jump Host → Target transfer.
This allows file-size validation to be controlled independently for each transfer step. 

Maintainer Notes

• The issue is dismissed as checking file sizes is useful only when applied to both transfer from/to jump host and transfer from/to remote host. Missing a file size check in one of the operations makes an integrity check pointless.
• Is is an option for users to apply the configuration to create hash files as this will guarantee integrity for all transfer steps involved.