Merge pull request #4369 from RosettaCommons/vmullig/fix_bad_unit_test
Fix a unit test that was invalidating the output of its own sub-tests.
The FA_ElecEnergy unit test suite's sub-tests were producing different results depending on whether they were run independently or as a suite. This was because the setup function called core_init(), while the first sub-test called core_init_with_additional_options( "-restore_pre_talaris_2013_behavior" ). Effectively, this meant that the sub-tests of the current defaults (which came later in the suite) were being performed against the -restore_pre_talaris_2013_behavior flag when the whole suite was run.
I'm correcting this by splitting the suite into two unit test suites with two different core_init() calls in the setup function. I'm also updating the expected values in the sub-tests that assumed that they were testing the current default scorefunction instead of the pre-Talaris 2013 scorefunction.