Ordering of state objects reversed for complex module expressions

[jjg-123]

In the ModuleExpression, the mechanism for resolving ambient variables was reversed, causing variables that were locally overridden to be ignored. This could not have been exposed without having a much more complex testing stack than in the unit tests, (thanks Robin!!) but a user did indeed get enough levels of scoping to trip this.

Solution is to swap two lines, and make sure the are loaded in the right order.