build constantly fails with "stdin: is not a tty"

`stdin: is not a tty` is not a serious problem, but why scp-action rollbacks and fails the whole build because of it? Can I make scp-action ignore this?

github actions log:

```
tar all files into /tmp/NKJYOrGgWZ.tar.gz
scp file to server.
create folder /home/***/releases
drone-scp error: stdin: is not a tty

drone-scp rollback: remove all target tmp file
remove file NKJYOrGgWZ.tar.gz
2023/08/*** 14:57:40 stdin: is not a tty
```

Start by reproducing the failure in a GitHub Actions workflow using scp-action, then trace the logged `stdin: is not a tty` message through the deployment and rollback behavior. The payload names no source file or test; done means this benign message no longer causes an unnecessary rollback or failed workflow.

Written by the indexing model from the issue text.