Invalidate cache itemstack and state after failed recipe completion

[ALongStringOfNumbers]

A couple changes related to #7

First, delay the recipe lookup until after there is confirmed to be a non-null item. Previously the recipe lookup would run before a guaranteed item was found, which means that recipe would always be null, even if the input check found an applicable item.

This change defers the recipe lookup to after finding an item, so that recipe will not be null (for an input item) after the new input item is set.

Secondly, if the input consumption failed due to null recipe or other factor, reset the cached itemstack and the mark state. This part is what addresses the issue in #7.

Fixes #7

[Exaxxion]

Changes look fine, having some weird issues with the runClient target in my local dev environment so would appreciate if someone can also verify the changes in game.

[ferreiraalex]

i can? release?

[Exaxxion]

This seems to fix the issue nicely. I had to make some changes to the build to fix my aforementioned runtime crash to finish reviewing, so we should merge #15 then this issue and we should be good.