[MCM-1349] Clone behavior changed and not versioned potentially breaking years worth of content

Partner Rank: 1

Verification builds:
1.17.0.54

Summary:
Clone behavior changed and not versioned breaking years worth of content

Impact:
The clone command is a command used in the bulk of adventure/mini-game experiences. The change of this command without it being versioned puts in jeopardy my last 4 years of content that used this behavior. At best, the unknown ramifications will result in buildings not appearing where they are supposed to, at worst, mechanics will stop functioning resulting in broken maps

Notable map impacts (will add as more are discovered):

Simburbia

Papercraft Adventure

Infinity Skyblock

Repro Steps:

download the repro world "clone change" from this bug report
create the world
press the button above the stone over and over

Observed Results:

the command now fails and does nothing and reports an overlap

this video shows me pressing a button and it not working in 1.17.0.54. https://www.youtube.com/watch?v=TjDi1-GKwmI

Expected Results:
the clone should work as it always has, and shift the redstone block over by 1 block each time, and if the change was intentional then it should be versioned in order to prevent huge swaths of back catalogue to stop working and/or have unintended consequences. this video shows the correct, working example in 1.17.0.52 ** https://www.youtube.com/watch?v=RqdNjHwnRmQ

Screenshots/Videos attached:

above. repro world is also attached

Regression Build:
has worked from at least 1.5 to 1.17.0.52

Notes:

The real problem with this being broken is that it is impossible to know the ramifications on the marketplace as a whole. The clone command is likely used in every map that uses mechanics of some sort so the likelyhood of this particular functionality being used in some way is high.

Even though it's "old tech" I even used it in Simburbia to mitigate another scoreboard problem I was having on PS4 that Mojang has been unable to fix, so now im in the situation where my contingency plan for players who do run into that bug is now also broken.