Better recipe validation

[bberkeyU]

Place for tracking differences for the recipe validation on github to build the .md .summary files as well as the populating the warnings.txt messages with more helpful values.

• ignore FOR or ENDFOR in comments.
• Add a warning when recipe is missing for example cookbook says RECIPE when filename is RECIPE.rcp
• Add {} around recipe command in warnings.txt ie eclipseObs.menu,synoptic-new.cbk,802_05wave_0.04step_2beam_16sums_4reps_both.rcp {data tcam 802.330 both 16} has invalid continuum
• Fixed the white space in the md files now we should have no leading space on the first line, and tabs for all the command spacing.
• Added checks for valid keyword arguments for most of the rest of the commands (previously only triggered on DATA.
• Add FOR/ENDFOR in .rcp files according to the LabVIEW source code. We only apply it in .ckb files right now. Currently, GitHub assumes any FOR/ENDFOR pair will get expanding regardless of what file they are in.
• Add nested FOR/ENDFOR expansion to github looks like labview supports this but github validator doesn't.