fix(grid): Fix calculate height when initially grid has no data #3950

[mpavlinov]

Closes #3950
Closes #3949
Closes #4745

Additional information (check all that apply):

• Bug fix
• New functionality
• Documentation
• Demos
• CI/CD

Checklist:

• All relevant tags have been applied to this PR
• This PR includes unit tests covering all the new code
• This PR includes API docs for newly added methods/properties
• This PR includes feature/README.MD updates for the feature docs
• This PR includes general feature table updates in the root README.MD
• This PR includes CHANGELOG.MD updates for newly added functionality
• This PR contains breaking changes
• This PR includes ng update migrations for the breaking changes
• This PR includes behavioral changes and the feature specification has been updated with them

[MayaKirova]

@mpavlinov This affects the HierarchicalGrid. In master by default if no height is specified for rowIslands in remote data scenario, they extend to their full content.
With this change now shrink to about 100px:

This will probably affect existing samples.
Perhaps we should add special handling for child grids, so that by default when no height is set it will act as height = null instead of height = 100% since child containers are small by default and won't look good in the default use-case.

[ChronosSF]

This seems to allow the vertical scrollbar to cover the last cells right edge before a horizontal scrollbar is shown. Why is this part of this PR?

I believe we moved the v scrollbar out of the tbody so that it never covers the cells.

[mpavlinov]

@ChronosSF There were failing tests. The issues was with the horizontal scroll that opened up a gap on the bottom. I fixed it by clearing the cache when the columns get recalculated.
Note: The issue is when the columns don't have widths set.

[ChronosSF]

@mpavlinov , if you don't have empty data but rather have initial data that can fit under what height 100% would usually be and then load the full data, you still get the grid to disable virtualization. I guess we need to derive the height on the data prop setter as well and not lose the initial setting. Not sure if this won't break something else though.