Enhancing FEProblem::reinitMaterials() interface

You can now specify whether or not the 'swap' step for stateful
materials occurs.

Refs #2379.
Fixes #2945 - Return value modified to return an empty block name when an output file name is forced for r7_moose/raven
Renamed [Outputs] related items (closes #2875)
Merge pull request #2948 from bobkinl/fix_2945

Fix RELAP-7/RAVEN mesh output hack in peacock.
Fixing a missing new line (closes #2957)
Merge pull request #2955 from aeslaughter/rename-2875

Renamed [Outputs] related items
Enforce MOOSE coding standards for #2951
Merge pull request #2958 from andrsd/fixing-new-line

Fixing a missing new line (closes #2957)
Fix to reset entire elasticity tensor, ref #2956
Merge pull request #2954 from dschwen/feature_2951

Cosmetic changes in the phasesfield module #2951
Defer periodicity to base class (closes #2953)
Merge pull request #2959 from jasondhales/elasticity_2956

Fix to reset entire elasticity tensor, ref #2956
Change Element so that it does not dervie from Material, ref #2960
Error checking for crack tip nodeset with multiple nodes in 2d closes #2963

For the case where the J-Integral is evaluated in 2d (even in a 3d model),
only only allow the crack tip nodeset to contain multiple nodes if they're
collinear.

Also, use range-checked parameter for 2d axis.  I had to change the name of
the parameter from 2d_axis to axis_2d to make the range checking parser happy.
Merge pull request #2961 from dschwen/feature_2953

Enable correct handling of periodic boundary conditions in MultiSmoothCircleIC  #2953
Fix gradient in MultiSmoothCircleIC (closes #2965)
Merge pull request #2966 from dschwen/feature_2965

Fix gradient in MultiSmoothCircleIC (closes #2965)
Merge pull request #2964 from bwspenc/j_2d_error_check

Error checking for crack tip nodeset with multiple nodes in 2d
Merge pull request #2962 from jasondhales/solid_mech_2960

Change Element so that it does not derive from Material, ref #2960
Recompute MaterialProperties for DiracKernels

* Reinitialize materials before computing Dirac kernels, but only
  if those DiracKernels actually call getMaterialProperty().

* Adding MaterialPropertyInterface::statefulPropertiesAllowed(bool).
  This allows classes derived from MaterialPropertyInterface to declare
  that they do not work with stateful material properties.  The only
  class which currently uses this functionality is the DiracKernel.
  The various getMaterialProperty*() interfaces have been updated to
  throw an error is stateful material properties are not allowed and the
  user asks for them.

  Note that only the MaterialPropertyStorage object knows if it has
  stateful material properties, so we had to provide an accessor from
  the MaterialData object which contains it that could be accessed by
  the MaterialPropertyInterface.

Refs #2379.