fix: adding sort for db out of order

[welbournR]

In the direct beam maker script the runs are now first sorted according to the Cd thickness before processing. This allows a consistent approach irrespective of which order they are measured. It also allows the flag for a different dead time correction to be applied to the largest Cd/lowest TOF dataset consistently.
It requires a load of the log twice but does not seem to have slowed down the processing.

Description of work:

Check all that apply:

• updated documentation
• Source added/refactored
• Added unit tests
• Added integration tests
• Verified that tests requiring the /SNS and /HFIR filesystems pass without fail

References:

• Links to IBM EWM items:
• Links to related issues or pull requests:

⚠️ Manual test for the reviewer

(Instructions for testing here)

Check list for the reviewer

• best software practices
  • clearly named variables (better to be verbose in variable names)
  • code comments explaining the intent of code blocks
• All the tests are passing
• The documentation is up to date
• code comments added when explaining intent