Loosen trait bounds in cw-orch-core

[Kayanski]

This Pr aims at loosening some trait bounds in cw-orch-core because theyr are un-necessary

[cloudflare-workers-and-pages]

Deploying cw-orchestrator with    Cloudflare Pages

Latest commit:	be82090
Status:	✅  Deploy successful!
Preview URL:	https://d86b11d3.cw-orchestrator.pages.dev
Branch Preview URL:	https://nicolas-orc-104-trait-bounds.cw-orchestrator.pages.dev

View logs

[codecov]

Codecov Report

Attention: Patch coverage is 91.66667% with 5 lines in your changes are missing coverage. Please review.

Project coverage is 64.7%. Comparing base (ff1e75d) to head (be82090).
Report is 3 commits behind head on main.

Additional details and impacted files

Files	Coverage Δ
contracts/counter/src/interface.rs	42.1% <ø> (ø)
contracts/mock_contract/src/lib.rs	97.9% <ø> (ø)
contracts/mock_contract/src/msg_tests.rs	94.7% <ø> (ø)
contracts/mock_contract_u64/src/lib.rs	83.3% <ø> (ø)
cw-orch-daemon/src/channel.rs	82.9% <100.0%> (ø)
cw-orch/src/snapshots.rs	97.5% <ø> (ø)
packages/cw-orch-contract-derive/src/lib.rs	93.0% <100.0%> (ø)
packages/cw-orch-core/src/contract/deploy.rs	0.0% <ø> (ø)
...ages/cw-orch-core/src/contract/interface_traits.rs	75.9% <ø> (ø)
packages/cw-orch-fns-derive/src/execute_fns.rs	99.2% <100.0%> (ø)
... and 2 more

[CyberHoward]

Can we loosen this bound as well? Could you search for all the uses of CwEnv in this library and replace them with their minimal requirements?

[Kayanski]

That's what I did yes ! And we can't loosen that bound because you need both QueryHandler and TxHandler to be able to use this trait !

[Kayanski]

emoved in the proc macros as well :)

[CyberHoward]

amazing, is this a breaking change to core?

[Kayanski]

amazing, is this a breaking change to core?

I'm not sure how to test that :/
Because we don't have abstract on that version, so it won't be all covering

[Kayanski]

amazing, is this a breaking change to core?

It shouldn't be, but I'm not sure there were not changes in the main branch that were breaking

[CyberHoward]

amazing, is this a breaking change to core?

It shouldn't be, but I'm not sure there were not changes in the main branch that were breaking

This is important for you to keep track of. You can go through commits on main and see if any of them are PRs that you expect to be breaking and look into them.