Weird Sticky Card interaction with Storage Drawers

[Exaxxion]

Describe the bug In testing the recent Sticky Card feature, I noticed a bizarre interaction with Storage Drawers that breaks normal network storage functionality. When all of the items in a drawer were extracted (usually from a large crafting request) the items formerly restricted to that drawer via a Sticky Card would refuse to enter the storage drawer thereafter and would dump unrestricted into lower-priority storage until I manually moved some of every such item back into the drawers and defragged my storage with an ME IO Port. This problem was so pervasive that I ultimately had to remove all of the Sticky Cards I was using for my network to stop randomly clogging.

To Reproduce

1. Attach a locked Storage Drawer to ME network storage via an unfiltered storage bus on a Drawer Controller.
2. Place an item stack inside of the drawer.
3. Insert another of the same item stack via a terminal, and observe that it works.
4. Remove both item stacks, and attempt to insert items again, and observe that it does not work.
5. Alternatively to (4), if you have other storage, the item will improperly insert into a lower-priority destination (like a storage cell in a drive) instead of the sticky-carded drawer.

Expected behavior Items would attempt to and successfully insert into the storage bussed drawer network with highest priority, rather than the Sticky Card forbidding items from being placed into the drawers and improperly routing these items into lower-priority storage.

Additional context Demonstrative video of the sticky card rejecting insertion of an item into a valid drawer under the aforementioned conditions https://github.com/AE2-UEL/Applied-Energistics-2/assets/11907282/b8bd8903-febb-4e86-b649-68635ce9585b

Environment

• Minecraft Version: 1.12.2
• AE2 Version: 0.56.5 + NAE2 1.6.3 (also occurred on 0.56.4 + NAE2 1.6.2)
• Forge Version: 14.23.5.2847
• Storage Drawers Version: 5.4.2

[IntegerLimit]

Note: Storage Drawers has a 5.5.0 release. However, this does not fix this issue, to my knowledge.