Fix potential memcpy overlap issue in RECOVER_BR_INFO for i64/v128 copy

[kylo5aby]

When copying single i64 or V128 values in RECOVER_BR_INFO, source and
destination memory regions may overlap, causing memcpy-param-overlap errors

Use temporary variables to separate read and write operations, preventing
the overlap issue.

This fix references the approach used in the other path (when arity != 1), which calls copy_stack_values, that function explicitly handles memcpy overlap.