InvalidPathname error for IBC recipient in splitter instantiate.

[SlayerAnsh]

Describe the bug
Seems like VFS cross chain address with ibc:// protocol is failing for splitter instantiate with cross chain recipient.

Error Code

Query failed with (6): rpc error: code = Unknown desc = failed to execute message; message index: 0: dispatch: submessages: reply: Generic error: Invalid Pathname, Some("\"ibc://andromeda/home/andr13qy7w6n6c0gqhc0506vpwd0yma0fzejctwz4qd\" does not exist in the file system"): instantiate wasm contract failed: execute wasm contract failed [CosmWasm/wasmd/x/wasm/keeper/keeper.go:662] with gas used: '776425': unknown request

To Reproduce
Steps to reproduce the behavior:

1. Choose any chain
2. Create splitter and add two recipient
3. Add a cross chain address with `ibc:///home/ to one of the recipient
4. Instantiate and check error

Expected behavior
Splitter should be able to instantiate and fund should be transferred properly to cross chain recipient.

Screenshots
NA

Environment (please complete the following information):

• IBC Devnet chains

Additional context
Seems like the issue might be due to check found in resolve path code for VFS.

 // As cross-chain queries are not currently possible we need to ensure the pathname being resolved is local
    ensure!(
        pathname.get_protocol().is_none(),
        ContractError::InvalidPathname {
            error: Some("Cannot resolve paths with protocols at this time".to_string())
        }
     )

CW-ORCH tests is also using splitter but didn't catch this error, this should also be checked and new test added to cover these edge cases