Address FileChannel.lock runtime exception, address aliquot rollup deadlock

[XingY]

Rationale

Deadlock as result of aliquot rollup calculation and search indexer.
File lock exception

Related Pull Requests

• Fix java.nio.channels.OverlappingFileLockException #5898

Changes

• Process rollup samples in ascending order to match that of indexer, to reduce deadlock
• Catch OverlappingFileLockException (RuntimeException) and throw IOException so it can be handled better downstream

[labkey-jeckels]

@XingY does this improve the upload experience or error messaging? Here's my local testing:

Set a breakpoint in FileUtil.copyFile(). Configure it to only suspend the thread. This makes it possible to have two uploads conflict with each other.
In two separate browser tabs, drag the same file into the files web part to upload them.
They'll both hit the breakpoint. Let them continue.

I get two error dialogs in the two browsers and the new IOException logged on the server. I see similar behavior with the original code.