bad_data::test_invalid_files fails during release verification

[alamb]

Describe the bug

While working on #6016 the release verification script fails like this:

---- bad_data::test_invalid_files stdout ----
thread 'bad_data::test_invalid_files' panicked at parquet/./tests/arrow_reader/bad_data.rs:64:9:
Found new file in bad_data, please add test: ARROW-GH-43605.parquet
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    bad_data::test_invalid_files

test result: FAILED. 51 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.75s

error: test failed, to rerun pass `-p parquet --test arrow_reader`
+ cleanup
+ '[' no = yes ']'
+ echo 'Failed to verify release candidate. See /var/folders/1l/tg68jc6550gg8xqf1hr4mlwr0000gn/T/arrow-53.0.0.XXXXX.Gs46gX0sT4 for de

To Reproduce

Expected behavior
Test should pass

Additional context

[alamb]

The issue appears to be that I was too clever in the tests -- they look for invalid files that are not added to the tests

THey don't fail on CI as the master branch has a pinned submodule, but the verification scripts just checkout whatever is at the head:

arrow-rs/dev/release/verify-release-candidate.sh

Lines 110 to 112 in 6e9751f

	# Clone testing repositories if not cloned already
	git clone https://github.com/apache/arrow-testing.git arrow-testing-data
	git clone https://github.com/apache/parquet-testing.git parquet-testing-data

I'll put in a workaround to get 53.0.0 out the door, but then we'll have to fix it for real subsequently