Avoid array allocation for moving to equal domain

[mppf]

Resolves #25741

chpl__coerceMove(_array) already has the ability to omit an array copy when the source and destination arrays refer to the same domain.

However, when the domains have equal value but are separate instances, chpl__coerceMove would allocate a separate array and then move elements into it from the original array.

This leads to unnecessary memory usage in some cases; for example, a recursive function that returns an array and so declares the return type.

This commit adds a mechanism for array implementations to provide a way to steal the data buffers from another array which can be used in this scenario. In some ways this is similar to doiOptimizedSwap. Note that doiOptimizedSwap cannot be used here because we want to avoid allocation for one of the arrays.

Future Work:

• add an implementation of doiBuildArrayMoving for more array types (most notably, Block, Cyclic, and Stencil arrays)
• figure out how to get this optimization working for arrays-of-arrays. Currently, they are disabled, because something is going wrong with correctly setting up the domain for the nested arrays.

Reviewed by @benharsh - thanks!

• primers pass with valgrind
• full comm=none testing
• full comm=gasnet oversubscribed testing