If you attempt to transfer a SecretBytes via remoting, the data is unusable on the remote end.

Unlike a Secret which can be passed via Remoting without issues to the remote end a SecretByte becomes corrupted on the remote end.

This is due to the CredentialsConfidentialKey being stored on the Jenkins controller filesystem so is (correctly) not available on the remote side in order to decrypt the data.

Split from #913