Try to fix grave/sarcophagus etc. not working

[Foxtr0t1337]

1. Added new prepatch TryFindBestBetterStorageForPatch
2. Rebuilt for release so that changes take effect

TryFindBestBetterStoreCellForPatch had been deciding which item should be removed from listerHaulables, which improves performance. But it had been checking SlotGroups only.
Patching TryFindBestBetterStorageForPatch and checking for NonCell could solve the issue of grave/armor rack etc. not working. #60

Tried several things. Nothing broke, and it solved said problem.

[bbradson]

So, first of, thanks for contributing again.
Your implementation for now does have a number of issues:

• It's compiled in debug mode, meaning there's gonna be log spam again. Release is the correct configuration for public releases.
• The method returning 0 differs from vanilla behaviour. I believe that should've been thing.PositionHeld to have the thing at the best cell's current position returned instead
• TryFindBestBetterStoreCellFor is often called directly, like always by the animal hauling jobgiver for example. All those times it wouldn't remove from ListerHaulables if the removal only happens in TryFindBestBetterStorageFor. That'd lead to a potentially significant performance degradation from having items not needing hauling continue to get checked for too long. Not sure how to cleanly fix that without overhead tbh, but fish's ThingsQueuedForRemoval is already a hashset so it could be viable to just have the current method continue adding, but let TryFindBestBetterStorageFor then remove from the queue again if there is better storage and then do another TryFindBestBetterNonSlotGroupStorageFor check when actually resolving the queue and removing
• The replacement for TryFindBestBetterStorageFor looks, as far as I can tell, more intrusive than it needs to be. The result being IHaulDestination container storage can be identified by the method returning true with an IntVec3.Invalid foundCell. This can be handled by a more compatible postfix too

[bbradson]

Thanks