Avoid copying already copied arrays in history

[SirYwell]

Overview

Description

When writing changes, we already have copies of the get and set data. That means we don't need (and shouldn't) copy it again. This reduces memory allocations in the history by around 90%.

Submitter Checklist

• Make sure you are opening from a topic branch (/feature/fix/docs/ branch (right side)) and not your main branch.
• Ensure that the pull request title represents the desired changelog entry.
• New public fields and methods are annotated with @since TODO.
• I read and followed the contribution guidelines.

[dordsor21]

Which command(s) was this tested with?

[SirYwell]

Which command(s) was this tested with?

Only //air, but bot copying at this point must be safe, otherwise the history would be broken already

[SirYwell]

I did some more testing (height brush, //replace with several masks) and didn't find any issues beyond what's already broken.
For example the angle mask breaks history already, but that is unrelated to copying the array.