Spark Test: Fix flaky TestCopyOnWriteDelete tests

[gabeiglio]

These test were timing out on our CI builds, doing some investigation this exact issue came out in a similar test, and applying the same fix worked

The test was also getting stuck locally when running:

./gradlew --stacktrace -Pquick=true -x javadoc :iceberg-spark:iceberg-spark-extensions-4.0_2.13:test -DscalaVersion=2.13 -DsparkVersions=4.0 \
 --tests "org.apache.iceberg.spark.extensions.TestCopyOnWriteDelete"

Note: I only saw this in spark 4.0, but seems harmless to backport it to all other versions

[github-actions]

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.

[github-actions]

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

[RussellSpitzer]

Sorry I missed out on this, is this still an issue now? I don't think i've seen CI break with this particular cause lately

[github-actions]

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.