Use a patch file to update the package in the result-cache-package-update e2e test

[SanderMuller]

Follow-up to #6086, as requested in review: converting the result-cache e2e tests to use a patch file instead of inline mutations.

result-cache-package-update now ships a local path-repo package (test/logger) and updates it with a committed updatePackage.patch that bumps its version, then composer update test/logger --no-cache re-mirrors it and changes its recorded reference in vendor/composer/installed.php. This replaces the inline php -r edit of installed.php and matches the patch-file style from #6088. I validated the full sequence locally: the cold run is clean, the reference changes on update, and the warm run still prints "Composer packages changed (test/logger); re-analysing only the files depending on them." and "Result cache restored. 1 file will be reanalysed."

result-cache-composer-lock keeps its jq content-hash change. Its composer.lock is gitignored and regenerated by composer install (per the earlier review here), so there is no committed file for a patch to apply against, and the test's whole point is to flip only the lock's content-hash without touching any package. The jq does exactly that.

[staabm]

thank you!