Add not dataAddrPtr assert in arraycopyEval for dstObj

[rmnattas]

For offheap, the arraycopy transformations uses the correct base object in the dstObj node instead of the dataAddrPtr load. To guard that asserts are added to check the dstObj node to not be a dataAddrPtr symbol.

Following: #20264
OMR version: eclipse-omr/omr#7500

TODO:

is it possible that optimizer transformed the arrayCopy tree to such an extent that secondChild doesn't have children anymore (for example, it is an aRegLoad or something like that)? two obvious problems: 1) is it still having isDataAddrPointer flag set? 2) getFirstChild will have or cause problems.
This comment is applicable to all files modified.

Idea is to check if node is marked as internal-pointer.