fix(graphcache): Fix blocking of legitimate reexecutions after teardowns

[kitten]

Resolve #2835

Summary

This fixes Graphcache blocking legitimate reexecutions triggerd by the UI. These reexecutions could be triggered due to the previously introduced looping protection #2737.

When an operation is torn down and reactivated without any other network request inbetween, then Graphcache wouldn't clean up the operations that'd be blocked from refetching. This meant that it'd erroneously block a legitimate operation triggered by the UI.

The protection is meant to only trigger requests that'd potentially infinitely trigger requests, i.e. non-network-only operations triggered by cache misses.

This has been addressed by adding a missing clean up call in reaction to teardowns.

Set of changes

• Add missing reexecutingOperations clean up to teardown handler
• Remove typings/build testing line that we added to test a Rollup+TS build issue