Modified CPUSolver to have locally allocated accumulator in transportSweep()

Made a small change to CPUSolver so that scalarFluxTally() is passed in thread-allocated arrays instead of references to global array. This eliminates what appears to be false sharing, and was causing a large performance degradation from that of ThreadPrivateSolver.

Now, CPUSolver seems to be at the same performance level as ThreadPrivateSolver and in addition does not use extra memory making thread-local copies of the FSR array.

There are other ways to prevent this false sharing, (adding padding to the global array, modifying scalarFluxTally() to use a scalar accumulator, etc.), but the performance differences seemed minor between any of these solutions. Perhaps one would be better than another depending on specific architectures, but for now this should do the trick.
Go ahead and remove the same lines from all of the SWIG interface files for each different compiler / floating point precision configuration, ie:

``openmoc/gnu/single/openmoc_gnu_single.i``
``openmoc/gnu/double/openmoc_gnu_double.i``
``openmoc/intel/single/openmoc_intel_single.i``
``openmoc/intel/double/openmoc_intel_double.i``
``openmoc/bgq/single/openmoc_bgq_single.i``
``openmoc/bgq/double/openmoc_bgq_double.i``

I think we will end up removing some of these different SWIG configuration files at some point, but they are still useful if you want to easily compare performance between versions of OpenMOC built using two different compilers, or double/single precision within the same Python script. So let's make sure all