Include both custom and vanilla DataManipulators in BlockSnapshots.

[JBYoshi]

"Include ALL the manipulators!" - Quote from someone or something, or maybe no one

Fixes https://forums.spongepowered.org/t/getting-sign-lines-from-changeblockevent-break/23461.
Fixes #2416.

I'm worried about side effects, though (for example, if the custom data gets saved off and conflicts with NBT data), so this may need quite a bit of testing.

[gabizou]

The original reason why we used only custom manipulators at the time for BlockSnapshots was over a discussion for performance when retrieving the manipulators for block states and tile entities and the spam that could be affected.

Can introduce some more performant code for block states such that on block state creation they already have all their manipulators and key values assigned (doesn't really increase load time since they'll be done before the game is even loaded).

[gabizou]

This won't actually fix any of the issues originally requested about getting Data from a TileEntity as if a BlockSnapshot still had a TileEntity in place. Due to the methods being used to efficiently clone as much data into a BlockSnapshot for phase tracking, none of these methods will populate the DataManipulators as you'd expect. The resolution is still to implement NbtProcessors.