If a Step was undefined, explain that to the user more clearly than cucumber does

[plocket]

Add it to the Scenario itself if possible.

Something including something like "Did you spell something wrong in one of the Steps? Check the documentation at https://suffolklitlab.org/docassemble-AssemblyLine-documentation/docs/automated_integrated_testing."

You can probably use the After hook and the arguments passed to that, as well as our own scope.AddToReport(). [We can use the scenario parameter. See our current After to see how we check for the status of the test that just happened.]

Example of using .AddToReport():

ALKiln/lib/steps.js

Lines 1132 to 1135 in 4668760

	scope.addToReport(scope, {
	type: `row`,
	value: `For security, ALKiln will avoid creating a screenshot for this error. It's possible a secret is being used on this screen.`
	});