Implement a better method of passing state

[reverendbedford]

Right now we pass in a huge list of parameters to update the material model state. This is both ugly and makes it very hard to extend to add new types of state descriptions (e.g. radiation dose).

We have the same problem when it comes to history variables. Right now we just pass around vectors of doubles. We need a way to label variables with names and accommodate non scalar state variables.

I think we could deal with both of these issues with the same data structure. Requirements:

1. Store scalars, vectors, symmetric 2nd order tensors (Mandel notation), and general 2nd order tensors along with an instance of this same data structure (to store history variables).
2. Be able to report which type each of the above has.
3. Associate a name with each variable and be able to retrieve variables by name.
4. Be able to marshal the struct into a flat vector and reconstruct the structure from the marshaled vector.

Objects would all need to be updated to:

1. Report what sort of state they need (both history and general state).
2. Take the state structs instead of flat vectors as input.

Interfaces would all need to be updated to:

1. Provide the struct instead of enumerated parameters (or a flat vector for history).

[reverendbedford]

The History structure provides all this for the crystal plasticity objects. "All" that would need to be done is to update the macroscale plasticity models to match.