FMSLogo Code

Apply the fix for Bug #598 to NAME.
This fixes a bug where NAME didn't behave correctly if the input variable name is name.variable.input or name.value.input.
As for QUEUE and DEQUEUE, the common case (when the procedure's parameter's don't shadow the variable to be assigned)
is executed within the procedure, not as the macro's output list.

Remove what may be redundant logic in begin_apply.
If I'm correct, this makes the complicated evaluator code a little simpler without introducing a regression.

The "if (tailcall <= 0)" block is redundant with what's in lambda_qm, which is what
gets executed if no error are encountered in the meantime.

I'm less confident about removing "tailcall=0", but it could be that this was only
done when the code called llocal() instead of add_variables_to_var_stack.
llocal() is a no-op when tailcall==0, but add_variables_to_var_stack executes
regardless of the value of tailcall.

Refactoring: Replace a for loop with no initialization statement with a while loop.
This makes the code structure clearer.

Refactoring: Move a local variable declaration and assignment closer to where the variable is first used.
This makes the code easier to read.

Update test log with output from new tests.

Fix Bug #600; A procedure which runs a tail-called APPLY no longer leaks its parameters into the caller's scope.

The fix was to split llocal() into two procedures, one that creates a variable scope and one that doesn't.
LOCAL uses the one that creates a new variable scope (no change).
evaluator() uses the one that doesn't (the fix).

This change diverges from UCBLogo's implementation, which also doesn't have this bug.
Therefore, there's at least one other way fix it. I'm not confident that I picked the right fix.

Add a bad input test to APPLY that crashes UCBLogo but not FMSLogo.
This is important, in case I cherry-pick changes from UCBLogo to fix problems in FMSLogo.

Rewrite some tests which log very long lines to instead log short lines.
This addresses a problem when using a side-by-side differ to compare the test log to the baseline test log.
Notably, meld has a limit of 8K characters per line.

Use wxSingleInstanceChecker to detect if another instance of FMSLogo is running on startup.
This prevents multiple instances of FMSLogo from running on GNU/Linux unless to they were given a specific program to run.
The CreateMutex logic on Windows was preserved until it can be confirmed that wxSingleInstanceChecker can grab the exact same mutex.
Otherwise, FMSLogo 8.5.0 couldn't detect if FMSLogo 8.4.0, the installer, or the uninstaller is running, and vice versa.

Refactoring: Rename NODETYPES to NODETYPE.
When the type was an "unsigned short", a plural made sense because it was the set of all possible types.
As an enum, a singular makes more sense, because it's the type of the associated NODE.