make run-integration-tests.sh update the integration tests Cargo.lock.

[lucasbalieiro]

as follow-up of #2026

to unblock #2029

This avoids "patch was not used in the crate graph" warnings when the version of a patched dependency changes and the lockfile still pins the old version.

[lucasbalieiro]

These lines were removed because a preceding sed command deletes content up to the first blank line.
The extra blank line triggered incorrect behavior in local sessions.
CI did not catch this because each CI run fetches sv2-apps from a clean state.

[plebhash]

why do we need to run cargo update?

we should add a comment explaining the motivations

[lucasbalieiro]

ammended a comment expanding the explanation of the PR description

diff --git a/scripts/run-integration-tests.sh b/scripts/run-integration-tests.sh
index 10362dacfb..f14aac4c28 100755
--- a/scripts/run-integration-tests.sh
+++ b/scripts/run-integration-tests.sh
@@ -122,15 +122,21 @@ fi
 
 # Add the patch section at the end of the file
 cat >> Cargo.toml << 'EOF'
-
 # Override dependencies with local paths
 [patch.crates-io] 
 stratum-core = {path = "../../../stratum-core"}
-
 [patch."https://github.com/stratum-mining/stratum"]
 stratum-core = {path = "../../../stratum-core"}
 EOF
 
+# Force a refresh of Cargo.lock so the patched stratum-core is not ignored after
+# a crate version change. When stratum-core's version changes, the lockfile may still
+# pin an older version, causing Cargo to ignore the patch entirely
+# ("patch was not used in the crate graph"). Running `cargo update -p stratum-core`
+# updates the lockfile to match the patched crate, ensuring the local override
+# actually takes effect.
+cargo update -p stratum-core
+
 echo "✅ Updated Cargo.toml to use local dependencies"
 echo "🏃 Running integration tests..."