Fix SFTP test failures in chrooted environments

[Copilot]

SFTP integration tests were failing with "No such file" errors due to incorrect path handling in chrooted environments where the server restricts users to a specific directory tree.

Changes

• Test setup: Handle empty SFTP_TEST_ROOT environment variable correctly - empty string now uses relative paths instead of defaulting to /tmp/sharpsync-tests
• Exception handling: Catch SftpPathNotFoundException in addition to SftpPermissionDeniedException during directory creation and initialization
• Chroot detection: Simplify logic to assume relative paths when RootPath doesn't start with "/", which correctly identifies chrooted servers

Example

// Before: Empty SFTP_TEST_ROOT defaulted to absolute path
_testRoot = Environment.GetEnvironmentVariable("SFTP_TEST_ROOT") ?? "/tmp/sharpsync-tests";

// After: Explicitly check for null to distinguish empty string (chroot) from unset
var testRootEnv = Environment.GetEnvironmentVariable("SFTP_TEST_ROOT");
_testRoot = testRootEnv ?? "/tmp/sharpsync-tests";

The CI test environment uses SFTP_TEST_ROOT="" to indicate a chrooted setup, but the code was treating this the same as an unset variable.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.