Downgrade Commons IO to prevent Android compatibility issues

[seadowg]

Closes getodk/collect#5579

What has been done to verify that this works as intended?

Verified manually.

Why is this the best possible solution? Were any other approaches considered?

Not a lot else to do here - the only alternative would be to make JavaRosa (and therefore Collect) only compatible with API 26+.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

I don't think there's much risk here. It is a bit scary downgrading as we are most likely bringing in bugs (from commons-io), but all tests are green (here and in Collect using this), so we're hopefully fine.

[seadowg]

@getodk/testers do we test with a device with Android 7.1.1 or lower as part of regression? Just want to check whether this is a gap in our testing or not.

[srujner]

@seadowg We used to have a single steps for a 5.1 in some test cases ~10, but we stopped checking it as we're mainly focusing on Android 10 and 13 and we have 8.1 for PRs

[lognaturel]

The Android version checker is supposed to help us with things like this but it doesn’t because it’s a runtime exception!

I don’t think we need to change our process. I’ll continue using older devices and if we don’t catch these kinds of problems before releasing we’ll see them in logs.