Add new test to check for early destruction of records

Records inside a global tuple are autoDestroyed too early when the
record contains a member with a type such as an array. This causes the
use of an invalid pointer, and can lead to segfaults, double frees and
similar errors.
Fix tuple early autoDestroy bug.

In cullExplicitAutoDestroyFlags(), expand the effect to also include "regular" insert auto
destroy flags.

This function removes the autoDestroy flags from values that are copied (through a move)
into the return value variable of a function.  The case that was resolved before dealt
only with explicit autodestroy flags, but since tuples are created through a call to
_build_tuple_always rather than a constructor call (which would be an explicit new), it is
necessary to add the "normal" auto destroy case to the routine.

The original code was written to be very narrow, to avoid surprises.  But testing should
reveal if there are any associated with this small expansion.
Move some record tests to a more appropriate directory.

These tests were living under test/arrays/ but they don't contain any arrays,
and are actually testing record functionality.  I decided to move them to
test/types/records because that seemed the more logical place.
Merge pull request #862 from lydia-duncan/reclassifyDeitzRecordTests

Move some record tests to a more appropriate directory [trivial]

These tests were living under test/arrays/ but they don't contain any arrays,
and are actually testing record functionality. I decided to move them to
test/types/records because that seemed the more logical place.
Merge pull request #860 from hildeth/fixTupleEarlyAutoDestroyBug

Fix tuple early autoDestroy bug.



In cullExplicitAutoDestroyFlags(), expand the effect to also include "regular" insert auto
destroy flags.

This function removes the autoDestroy flags from values that are copied (through a move)
into the return value variable of a function. The case that was resolved before dealt
only with explicit autodestroy flags, but since tuples are created through a call to
_build_tuple_always rather than a constructor call (which would be an explicit new), it is
necessary to add the "normal" auto destroy case to the routine.

The original code was written to be very narrow, to avoid surprises. But testing should
reveal if there are any associated with this small expansion.

[t: std, --verify, --no-local, gasnet(distributions)]
Merge pull request #857 from Kyle-B/kb-add-record-tuple-test

Add new test to check for early destruction of records