Containers sometimes leave items hanging around origin

• If an ingredient is placed in a crockpot and then rots, then the spoiled food hangs around the origin
• If a medium fish (dogfish, swordfish) is placed in an icebox and then rots, then the spoiled fish hangs around the origin
• If a doydoy is on a full shelf (Hamlet) and then starves, most of its loot (feathers, drumsticks) hangs around the world origin
• If you open a shelf with controller, fill 5/6 slots with coconuts and keep the last slot empty, and then switch to mouse to use a machete to hack a shelfed nut, then a half nut hangs around the origin

The common thread between these bugs is that the Container:GiveItem method inappropriately refuses to drop on fail even when the drop_on_fail parameter is specifically set to true (or if it's set to nil, which is meant to default to true). The above scenarios are attributable to the following two issues.

• The GiveItem method begins by immediately calling CanTakeItemInSlot, but if that returns false then nothing happens and the item doesn't get dropped. This happens in the first 3 scenarios above.
• If you try to put a stack into an empty slot of a non-stacking container, then GiveItem fills one slot with one item but then returns false while unilaterally refusing to drop the rest of the items. This happens in the last scenario above, with coconuts on shelves.

I scoured the files for every case where the Container:GiveItem method was called, and I'm fairly certain that in every case we expect it to drop on fail unless specifically told not to. Certainly that's the expectation in the four examples I found, and we get weird behavior since GiveItem isn't doing what it's supposed to.