[bug] RustBCA should emit warning when conflicting options are active, or when input parameters conflict with input options

[drobnyjt]

Prime example of this behavior is when track_recoils = false and track_displacements = true - the former deactivates the latter, and if one is editing input files by hand, the problem may not be immediately apparent.

[drobnyjt]

Following from discussion in issue #258, I will extend this issue to include raising warnings for at least the following situations:

• Lindhard-Scharff stopping used for incident energies above 25 keV/amu
• weak collisions used for Z1 >> Z2
• extremely low energies (for which RustBCA can, depending on the details, be used to produce acceptable results, but each ion/target pair should be verified against experiment or high fidelity modeling first) or extremely high energies (Biersack-Varelas stopping does not include radiative effects)
• using example values in materials.py

I will continue to add to this list as issues appear.

[drobnyjt]

A warning has been added to materials.py.