Disconnected Lodestone compasses stacking issue from lodestone compasses of diff. origins

The bug report’s title had to be shortened down due to the bug report title character limit.

The bug:

Disconnected Lodestone compasses, where each compass was originally from a different linked lodestone which has since been broken, won’t stack with each other. This is in contrast to Java, where all disconnected lodestone compasses can stack with each other regardless of their original lodestone origins if their lodestone ever broke.

Steps to Repro:

1. Place a lodestone on your left

2. Place a lodestone on your right

3. Get 2 compasses

4. Link one compass to the left lodestone

5. Link one compass to the right lodestone

6. Break the left lodestone

7. Break the right lodestone

8. Try stacking the 2 lodestone compasses together

Observed Results:

The disconnected lodestone compasses don’t stack. That is because the trackingHandle NBT tag is still present, which may hold different integers depending from which lodestone they were linked to even after the lodestone is gone.

Expected Results:
The disconnected lodestone compasses stack like Java.

The Fix:

A disconnected lodestone compass has to clear out its trackingHandle NBT tag just after the moment it realises it’s original lodestone is truly gone from the world. To ensure older disconnected lodestone compasses can stack as well from prior to the fix, the trackingHandle NBT is also cleared out if it has already known it’s original lodestone is truly gone from the world upon the item next loading in the world.