save SSH_AUTH_SOCK and SSH_AGENT_PID before reading GPG_ENV

GPG_ENV possibly contains SSH_AUTH_SOCK and SSH_AGENT_PID from a
gpg-agent previously started with the ssh agent built-in functionality
enabled. If an ssh-agent is already live, we should use the existing
ssh-agent's environmental variables rather than the old variables from
the GPG_ENV file.