Add distant wasm upload

[Kayanski]

This PR aims at providing integrators with more methods to query the wasms to upload on chain.

Checklist

• Changelog updated.
• Docs updated.

[cloudflare-workers-and-pages]

Deploying cw-orchestrator with    Cloudflare Pages

Latest commit:	e1ef1e9
Status:	✅  Deploy successful!
Preview URL:	https://4ac93bfa.cw-orchestrator.pages.dev
Branch Preview URL:	https://add-distant-wasm-upload.cw-orchestrator.pages.dev

View logs

[Kayanski]

This is just a copy of the old artifacts_dir module inside wasm_path.rs

[CyberHoward]

I'm surprised by how much code was changed for this feature, and it's breaking to cw-orch-core.

is there no alternative way that we could structure this PR to make it non-breaking?

[Kayanski]

I'm surprised by how much code was changed for this feature, and it's breaking to cw-orch-core.

is there no alternative way that we could structure this PR to make it non-breaking?

Yes. this was done to propose a preliminary implementation.
The issue here is that the current cw-orch-core version exposes WasmPath(PathBuf), which we need to modify to accomodate for this change.
An additional option we could use is to have an additional method inside the Uploadable trait for fetching the contracts remotely. This is not ideal, but could be experimented.
Removing the associated cw-plus changes to make things clearer

[CyberHoward]

And what about separating the fetching from the rest of the logic? I.e. adding a fn or object that you can use to fetch any wasm blob and store it in the local / configured artifacts folder?

I guess that complicates other things like sharing the crate and then needing to resolve where to store + retrieve the file...