Unify noop and test renderer assertion APIs (#14952)

* Throw in tests if work is done before emptying log

Test renderer already does this. Makes it harder to miss unexpected
behavior by forcing you to assert on every logged value.

* Convert ReactNoop tests to use jest matchers

The matchers warn if work is flushed while the log is empty. This is
the pattern we already follow for test renderer. I've used the same APIs
as test renderer, so it should be easy to switch between the two.

src/__tests__/ReactTestRenderer-test.internal.js

@@ -1018,7 +1018,7 @@ describe('ReactTestRenderer', () => {
       </Context.Provider>
     );
     ReactNoop.render(<App />);
-    ReactNoop.flush();
+    expect(ReactNoop).toFlushWithoutYielding();
     ReactTestRenderer.create(<App />);
   });