Correctly handle `Input::Message` when calling `msg_sender()` #20428

Job	Run time
build-sway-examples	1m 23s
build-sway-lib-core	4m 30s
build-sway-lib-std	1m 11s
get-fuel-core-version	49s
build-reference-examples	4m 47s
check-sdk-harness-test-suite-compatibility	42s
forc-fmt-check-panic	1m 53s
forc-fmt-check-sway-examples	3m 49s
forc-fmt-check-sway-lib-core	4m 0s
forc-fmt-check-sway-lib-std	1m 1s
build-forc-test-project	11m 16s
build-mdbook	6m 1s
build-forc-doc-sway-lib-std	5m 59s
cargo-build-workspace	3m 48s
cargo-clippy	1m 3s
cargo-run-e2e-test-evm	8m 36s
cargo-fmt-check	14s
cargo-toml-fmt-check	15s
cargo-run-e2e-test-midenvm	8m 36s
cargo-test-lib-std	2m 39s
cargo-test-sway-lsp	5m 16s
cargo-test-workspace	13m 3s
forc-pkg-fuels-deps-check	16s
cargo-unused-deps-check	4m 11s
forc-run-benchmarks	3m 27s
forc-unit-tests	1m 54s
pre-publish-check	0s
cargo-test-forc-debug	4m 21s
cargo-run-e2e-test	12m 20s
cargo-run-e2e-test-release	13m 13s
cargo-test-forc-client	3m 26s
notify-slack-on-failure	6s
publish	0s
build-publish-master-image	0s
build-publish-release-image	0s
Build and upload forc binaries to release	0s
	2h 14m 5s

Provide feedback