Added enable Bruker Detector checkbox for EXAFS Scan view and 2D map scan view. Change the default name of EXAFS scan to 'EXAFS scan'
Added enable Bruker Detector to 2D/EXAFS scan configure and connect it with the Scan Configuration View. Also made changes to the Oxadation Scan Configuration View, so that it matches with the 2D scan Configuration
Altered:
- fixed a bug where the SMAK data file (and only the SMAK file) was accidentally not exporting any data when scans fully completed.  (you know... the standard case....)
Add enable Bruker Detector checkbox for 2d Oxidation scan configuration
view
Add check for enableBrukerDetector of ScanConfiguration for scan controller.
Enable Bruker Detector by default
Altered:
- Moved the enableBrukerDetector flag and member functions from the scan configuration subclasses to the SXRMBScanConfigurationDbObject and SXRMBScanConfiguration.
- Changed the call in AMEnergyListView to build the regions based on the count in the list we're creating, not the existing energy list.
- Changed semantics for setEnableBrukerDetector to check for inequality rather than equality, to mirror other similar functions.
- Changed semantics for buildScanControllerImplementation() in the scan controllers to place some actions inside of a check rather than failed out if the bruker is not enable, just trying to be future proof.

Added:
- Database parameter declaration for enableBrukerDetector flag to the SXRMBScanConfigurationDbObject so it will be saved.

Also changed a bunch of indentation.
Merge pull request #1041 from acquaman/Issue1010

Should be good to go. Made a few changes while @dretrex and @XuetaoLiu-CLS  were working on a different problem. Did preliminary testing and it appears to be work.
Added:
- A scan axis validator method to SXRMB2DMapScanConfigurationView where
it changes the step spin box background colour to red if the start and
end points don't create a valid axis.  It also brings up a big red text
label to tell you what you did wrong.  Unfortunately, it does not stop
the program from crashing if users insist on trying to start a scan with
invalid axes.
- Changed the step spin box minimum values to be 0 to prevent the
possibility of setting negative step values.
- In SXRMB2DScanActionController, we added fabs to check scan axes are
valid.
Fixed merge conflicts.
Solve merge conflictions
- A scan axis validator method to
SXRMB2DOxidationMapScanConfigurationView where
it changes the step spin box background colour to red if the start and
end points don't create a valid axis.  It also brings up a big red text
label to tell you what you did wrong.  Unfortunately, it does not stop
the program from crashing if users insist on trying to start a scan with
invalid axes.
- Changed the step spin box minimum values to be 0 to prevent the
possibility of setting negative step values.
- Adjust the location of enable Bruker Setting widget to the right
bottom of the screen
- Move the enable Bruker Detector groupbox of EXAFS scan to the right-
- Change the Scan name groupbox of oxidation map scan configuration to
"Scan Information"
- Adjust the codes a little bit
FIXED:
Added else statement to hande case where no exporters are registered in
AMExportWizardOptionPage::populateOptionSelector()
Modify buildProject script to support make only option
Merge pull request #1055 from acquaman/Issue1032

Pull request for Issue #1032 REIXS Crashing on export
Merge branch 'master' into Issue1034