[Follow-up] Investigate if we need to optimize EntityInterface::setOriginal() to only clone when not set

I think this follow-up is the wrong way round :)

The clone *is* the optimization, the alternative is loading the whole entity again. The question is whether it's worth keeping that (IMHO yes, especially for bulk saves).

In a way, I think this is covered by this existing old issue: 🐛 $entity->original gets stale between updates Needs work . Removing/deprecating the ability to preload original prevents us from fixing that.

Oops, guess my coffee didnt set in, then this could be closed i guess.