Add volumetric optical physics

[sethrj]

Cross section tables

Split off from #886 . I think this could be a good opportunity to explore a new design for building physics tables that can be extended to satisfy #907 and #253 .

First, I think to keep the Model (or OpticalVolumeProcess) interface simple, we should have a single virtual method that takes or returns a relatively complicated object for the cross section construction. In ORANGE, for constructing surfaces and numerous other data structures from a "Solid" factory object, the model of passing in a Builder class (which has wrappers for the various CollectionBuilder methods) has worked really well.

So perhaps our class would have:

virtual void build(XsBuilder&) const = 0;

and XsBuilder would have:

• Accessors for getting the optical material data, properties, cutoffs, etc.
• Internally a GenericGridBuilder for adding the cross section data
• A method like insert_xs(OpticalMaterialId, SpanReal energy, SpanReal xs) with error checking to make sure that it's called once per material for all materials

Then during construction, the OpticalPhysics will:

• Construct a temporary XsBuilder
• Loop over all OpticalVolumeProcess to construct the XS data
• Generate total cross sections, etc.

Models

• Absorption: Add optical absorption model with imported data #1440
• Rayleigh: Implement optical Rayleigh model #1469
• WLS: Add an Optical WLS #1507

[hhollenb]

I made a rough draft of an idea I had for splitting out some of the builder functionality:

hhollenb#1

I'm not fully happy with it, but there might be something there that could be refactored into something useful.

[sethrj]

Thanks @hhollenb ! There are some good ideas there but I'm not sure how we can make them reusable/general without sacrificing clarity/robustness...

[sethrj]

Tagging #1469