Refs #10090. POLDI chopper speed is rounded to next 500
Refs #10090. Refactored chopper parameter loading process.
Merge branch 'master' into feature/10090_correct_poldi_chopper_speed
Refs #10090. Added extractor for chopper speed target

As it turns out, the chopper speed target is stored as integer list, so the value needs to be converted.
Refs #10090. Added POLDI definition 2014b

The instrument definition is required for the adjusted system test.
Refs #10090. Forgot to remove debugging statement
Refs #10090. Changed PoldiTruncateData.

As indicated in the comment in PoldiTruncateData, the chopper loading should have been replaced immediately after #9445, but since that did not cause problems with old data files, it was not necessary. Now it uses the code in PoldiInstrumentAdapter and PoldiTruncateData also works with new data files where the chopper speed is off.
Refs #10090. Disable entry in poldi.dic

In some POLDI data files the field with chopper rotation speed target information seems to have some problems. Disabling this field in poldi.dic disables the check for chopper speed matching the target, while the rest of the functionality is preserved.
Merge remote-tracking branch 'origin/feature/10090_correct_poldi_chopper_speed'