Add tests for concurrent origin 404s

We have observed issues with high memory usage from timers with heavy concurrent cache resolution from origin that results in 404/undefined results (which are not cached by default, #153). We should create tests to verify if there are any issues with timer memory amplification.