[table] Flakiness in TableQuadrantStack tests

[ggdouglas]

CircleCI test insights identify the "Scroll syncing onScroll" tests of TableQuadrantStack as our most flaky test suite. We should skip these tests until we can rewrite them to be more reliable.

blueprint/packages/table/test/quadrants/tableQuadrantStackTests.tsx

Lines 565 to 596 in 2666835

	describe("onScroll", () => {
	// "wheel" is invoked before "scroll"; both listeners may invoke
	// onScroll, but we want it to be invoked just once on each "wheel"
	// event. thus, use the stricter `calledOnce` instead of `called`.
	it("invokes onScroll on MAIN quadrant scroll", () => {
	TestUtils.Simulate.scroll(mainScrollContainer);
	expect(onScroll.calledOnce).to.be.true;
	});
	it("invokes onScroll on MAIN quadrant wheel", () => {
	TestUtils.Simulate.wheel(mainScrollContainer);
	expect(onScroll.calledOnce).to.be.true;
	});
	it("invokes onScroll on TOP quadrant wheel", () => {
	act(() => {
	TestUtils.Simulate.wheel(topScrollContainer);
	});
	expect(onScroll.calledOnce).to.be.true;
	});
	it("invokes onScroll on LEFT quadrant wheel", () => {
	TestUtils.Simulate.wheel(leftScrollContainer);
	expect(onScroll.calledOnce).to.be.true;
	});
	it("invokes onScroll on TOP_LEFT quadrant wheel", () => {
	TestUtils.Simulate.wheel(topLeftScrollContainer);
	expect(onScroll.calledOnce).to.be.true;
	});
	});

https://app.circleci.com/insights/github/palantir/blueprint/workflows/compile_lint_test_dist_deploy/tests