Sanitize paths for SSH data

[MarkEWaite]

Sanitize paths for SSH data

SSH has special rules related to '%' characters in its file name arguments. Refer to the ssh_config man page for its descriptions of tokens:

https://man.openbsd.org/ssh_config#TOKENS

If the absolute path to the temporary file for the private key includes a '%' character, then use the system temporary directory instead.

Likewise if the absolute path to the Windows temporary file for the private key includes a ' ', a '(', or a ')', then use the system temporary directory.

Windows

Makes the createTempFile() implementation match the comment.

Fixes #1704

Fixes #1710

Amends 5a271e5

Testing done

• Confirmed that I can duplicate the bug with a multibranch Pipeline cloned through an SSH URL when one of the branches in the repository contains a '/' character. In my test case, I used 'bug/git-cleint-plugin-1710' as the branch name
• Confirmed that the bug is resolved by this change

Multibranch Pipeline definition used for test:

pipeline {
    agent {
        label 'windows'
    }
    options {
        skipDefaultCheckout true
    }
    stages {
        stage('Checkout') {
            steps {
                ws('percent%2Fencoded') {
                    checkout scm
                }
                ws('a b') {
                    checkout scm
                }
                ws('c(') {
                    checkout scm
                }
                ws('d)') {
                    checkout scm
                }
                ws('e())') {
                    checkout scm
                }
                ws('f g') {
                    checkout scm
                }
            }
        }
    }
}

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed