Create structured validation and verification cases for Zapdos

[cticenhour]

We should adopt a more consistent format for any V&V cases we seek to add. I should suggest starting from the example set by another MOOSE-based code, TMAP8 (https://mooseframework.inl.gov/TMAP8/).

In their V&V page (https://mooseframework.inl.gov/TMAP8/verification_and_validation/index.html), they have several common elements:

• Consistent sections / elements:
  • Description / Introductory information
  • Benchmarks discussion or differences (if comparing against another code)
  • Experimental discussion (if applicable)
  • Analytic solution (if applicable)
  • Results and comparison to experiment/solution
  • Input files used to run the case, and any relevant discussion on their structure, how the capability is tested, etc.
  • References
• Heavy usage of references
• Usage of source code, input file, or test specification links or inclusion of snippets to provide relevant context.

I think this promotes being thorough in development of our tests and examples, and provides ready-made onboarding documentation for those interested in learning more about what Zapdos can do.