[DataGridPro] Use intersection observer to trigger server-side infinite loading

[arminmeh]

I have extracted IntersectionObserver logic into a separate hook and moved it to the server side feature folder, since the client side feature is deprecated.
Both client and server side infinite loading are now listening to the new internal event from this hook to handle the data update

There are two main reasons for doing this:

1. With the intersection observer we are covering more cases where the new data fetch should occur. One of them is if the page size is not big enough to fill the whole viewport. With the observer additional data is fetched until the viewport is filled.
2. IntersectionObserver events are far less frequent than scroll events, so handling those reduces the impact on the grid performance

[mui-bot]

Deploy preview: https://deploy-preview-17369--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 14c7c4d

[MBilalShafi]

Event names usually don't contain "on", it's the handler which contains it. For example, "click" event, and the corresponding handler would be "onclick". How about making it "intersectionObserved" or simply "intersection"?

Suggested change

	onIntersection: {};
	intersection: {};

[cherniavskii]

Perhaps calling it rowsScrollEndIntersection would be more meaningful?

[arminmeh]

I would go for intersection because this hook does not know where the trigger element is placed

Update:
Well, this is not entirely true
hook is using scrollEndThreshold prop and adding bottom margin to adjust the intersection area
so, even though you can place the element anywhere, it will not work anywhere

I will use rowsScrollEndIntersection

it is internal event anyway.
once/if we decide to make it generic, we can change this alongside with the other suggestion from #17369 (comment)
in that case, the check #17369 (comment) should also be completely removed