Add a test that noinit works with complexes

I realized that while I tested this case, I didn't commit a test for it.  Seemed
like a good thing to do.
Add a test on the use of --no-use-noinit with complexes

I also neglected to add a test for complexes here.  This is particularly
relevant, because the module definition of complexes requires noinit always be
honored, due to the implementation of type defaults in module code.  It is our
intention to alter the type default implementation, and in such a way that
noinit can be skipped in the modules when --no-use-noinit is through.  This
test ensures that complexes work before and after such a change takes place,
(it would be one of many tests that would fail if the implementation of
--no-use-noinit were broken, but its presence should indicate more quickly what
precisely has gone wrong).
Merge pull request #1036 from lydia-duncan/noinitComplexTest

Noinit complex tests [not reviewed]

I realized I forgot to add a noinit and --no-use-noinit test
involving complexes. The noinit case is more a sanity
check, but the --no-use-noinit test ought to be a good
indicator of what went wrong (and when something
goes wrong) should complexes fail again. The reason
they don't fail right now is because --no-use-noinit
does not affect the use of noinit within the standard
and internal modules. The determination of the
default value for complexes relies on noinit being
applied, at the moment. We expect that to change in
the future, and this test will make sure that complexes
continue to work throughout.