IMAT (nGEM detector): Scientists would like to test improved end of run script on nGEM PC

# Issue Description

As a scientist using the nGEM detector on IMAT, I am experiencing very slow processing times of the .edb files back to a .nxs files after they have been copied to server storage.

I have a modified Mantid script which I would like the nGEM PC to run on the .edb files locally to generate the .nxs file on the data area on the nGEM PC. This could then be moved by an automatic camera file task (as with other imaging cameras) to the NDX to be archived automatically. Even with new storage, this might still be the easiest way to get the desired .nxs file into a state where it can be uploaded by ADA.

### Additional Information

_{What else do I need to know before starting?}

- IMAT scientists/nGEM detector people can supply details of files/locations.
- Performance locally _may_ be an issue, but local code on a fast machine to SSD storage should give some guidance as to how this might be improved.
- Note that this depends (at a minimum) on editing a time binning number in the script. Possibly keeping this in a separate file if users need something simple to edit.

# Acceptance Criteria
- New script is tried out before next cycle on a test set of representative `.edb` files copied back to the nGEM PC
- Scientists can check results and decide how well this works (does it save later online processing - and how much)
- If it looks useful, ensure the scientists have what the need to do this for themselves (simple instructions?).

Start with the modified Mantid script and the nGEM PC data area, using representative .edb files copied back to the PC. Measure local processing into .nxs files and have IMAT scientists check whether the results reduce later online processing. Done means the script has been tried before the next cycle and, if useful, scientists have simple instructions to run it.

Scritto dal modello di indicizzazione a partire dal testo della issue.