Virtualization with big merge cells solution

[underfisk]

Its known that when the first merge cell parent is not visible all the merge cell effect is lost therefore there are 2 possible solutions:

1. Create a map with useMemo that calculates ahead of time whether the parent is visible or not and the first children will get the merge control but all the navigation, editors and behaviours that were on the main parent would have to be delegate to this child. Also the navigation must be adjusted if the user was on that parent that is not visible and pass it to the new one
2. Adjust react-virtualized cellRangeRenderer (https://github.com/bvaughn/react-virtualized/blob/master/docs/Grid.md#cellrangerenderer) and ensure that the merged cell parent plus its childs are rendered but this could negatively impact the application performance, therefore, will just be considered after attempting the creation of the first solution
3. Re-write the whole table instead of using react-virtualize under the hood we create our tables using default html tables that provide col/row spanning and we manage the virtualize with it (My preferable choice)