remove findDOMNode usage in Table component

[henryqdineen]

The React findDOMNode() API has been deprecated since 2018 and will be removed in React 19, the next major version. This PR removes findDOMNode usage from the Table component for compatibility with Strict Mode and to move towards React 19 compatibility. The WindowScroller and CellMeasurer components also use findDOMNode() but have existing workaround by using the registerChild from the render callback.

My solution in this PR was to add a getDOMNode method on the Grid class and call that from Table. An alternative I considered is to add a new ref domNodeRef to Table and use that to get the reference.

Before submitting a pull request, please complete the following checklist:

• The existing test suites (npm test) all pass
• For any new features or bug fixes, both positive and negative test cases have been added
• For any new features, documentation has been added
• For any documentation changes, the text has been proofread and is clear to both experienced users and beginners.
• Format your code with prettier (yarn run prettier).
• Run the Flow typechecks (yarn run typecheck).

[henryqdineen]

I totally missed that this overlapped with #1855. Please close if this PR is unwanted. This is based on a patch-package we did on our version. We are also interested in fixing any defaultProps related deprecation issues but this PR strictly focuses on findDOMNode().

[henryqdineen]

Now that React 19 is out I think #1855 should be preferred since it fixes the defaultProps gotchas.