* [pipes/crafting] Implemented event handler which should try to fulfill crafting orders with incoming unrouted items. There's still no fullscan of orders list [#225]
* [pipes/crafting] Now order result is injected into pipe via conventional interface. Routing and completed order removal is handled by eventHandler [#225]
* [pipe/crafting] Extracted crafting result lookup into separate method [#225]
* [pipes/crafting] Refactored active retrieval of crafting result
Notes on refactoring:
1. The whole block 'pull items-route items' extracted to a separate method
2. Extracted stack isn't split, since we always extract a minimum of item quota, order's quota and item's stack size, so there won't be a situation where we receive more than required to fulfill single order or more than we can send as single stack
3. Due to 2, we don't need to re-init order variable with existing stack; as a consequence, we don't need to remember if we were using crafting order or extra order.
[#225]