Using Remote SSH extension (ms-vscode-remote): [cfn-lint] Unable to start cfn-lint (Error: spawn /bin/sh ENOENT). Is cfn-lint installed correctly?

#### version & path
While connected to remote SSH host:

```bash
$ which cfn-lint
/home//.local/bin/cfn-lint

$ /home//.local/bin/cfn-lint --version
cfn-lint 0.54.4

$ cfn-lint --version
cfn-lint 0.54.4

$ cat ~/.bashrc | egrep PATH
export PATH=/home//.local/bin:$PATH
```

#### vscode general: settings.json

With vscode-fn-lint 0.2.2 version
But when I load a CloudFormation script into VSCode, I get the following error:
`[cfn-lint] Unable to start cfn-lint (Error: spawn /bin/sh ENOENT). Is cfn-lint installed correctly?`

#### vscode extension: @ext:ms-vscode-remote.remote-ssh,ms-vscode-remote.remote-ssh-edit
```json
"cfnLint.path": "/home//.local/bin/cfn-lint ",
```

All recommendations mentioned here have been followed with no resolution: https://github.com/aws-cloudformation/cfn-lint-visual-studio-code/issues/21

Any help would be appreciated.
Thanks!

The report names no repository file, test, or entry point. Start by reproducing the cfn-lint startup failure while connected through the Remote SSH extension, then trace how the extension launches cfn-lint and verify the behavior with the reported executable path. Done means remote SSH users no longer receive the spawn /bin/sh ENOENT error when cfn-lint is installed.

Written by the indexing model from the issue text.