fix: add missing ipfsNodeURL parameter in IExecDataProtectorModule

This fix ensures that custom IPFS node URLs (e.g., local IPFS for testing)
are properly passed to the internal IExec instance.

Without this fix, tests using local IPFS (like Docker Compose setups)
fail with connection timeouts to production IPFS nodes because the IExec
instance was using default chain IPFS URLs instead of the custom configured ones.

Changes:
- Added ipfsNodeURL: ipfsNode to the IExec constructor options
- This parameter was already extracted from config but never used
- ipfsGatewayURL was already being passed, making this a missing piece

Impact:
- ✅ Tests with local IPFS now work correctly
- ✅ Custom IPFS configurations are properly respected
- ✅ No regression for production (spread operator still allows override)
- ✅ Consistent with ipfsGatewayURL handling

Author: abbesBenayache

packages/sdk/src/lib/IExecDataProtectorModule.ts

@@ -118,6 +118,7 @@ abstract class IExecDataProtectorModule {
         { ethProvider: this.ethProvider },
         {
           ipfsGatewayURL: ipfsGateway,
+          ipfsNodeURL: ipfsNode,
           ...this.options?.iexecOptions,
           allowExperimentalNetworks: this.options.allowExperimentalNetworks,
         }