Fixed EuiInMemoryTable content render on changing pagination

[hetanthakkar]

Summary

Fixed issue #3231 Disabling pagination will render the whole content in the table and enabling it will again allow pagination in the table

Checklist

• Check against all themes for compatibility in both light and dark modes
• Checked in mobile
• Checked in Chrome, Safari, Edge, and Firefox
• Props have proper autodocs and **[playground toggles](https://github.com/elastic/eui/blob/master/wiki/documentation-guidelines.md#adding-playground-toggles)**~
• Added documentation
• Checked Code Sandbox works for the any docs examples
• Added or updated jest tests
• Checked for breaking changes and labeled appropriately
• Checked for accessibility including keyboard-only and screenreader modes
• A changelog entry exists and is marked appropriately

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[hetanthakkar]

@chandlerprall @cchaos Could you please review!

[thompsongl]

Thanks for the PR, @hetanthakkar1!
We'll review this soon. In the meantime, can you please check off the tasks you've completed in the "Checklist?" If any tasks don't apply to this PR, you can strike-through the item. Having an accurate Checklist helps us see what's been completed.

[hetanthakkar]

@thompsongl Sure! Thank you

[hetanthakkar]

@cchaos @chandlerprall @thompsongl Could you please review!

[thompsongl]

jenkins test this

[thompsongl]

Code changes LGTM; thanks, @hetanthakkar1

Just some changelog clean up.

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4714/

[hetanthakkar]

@thompsongl I have made the necessary changes. Could you please review!

[hetanthakkar]

@thompsongl I was just curious and wondering that you maintainers after reviewing our PR usually test them by writing Jenkin, Test this. But if we contributors are also given the freedom to do that I think the process can speed up and save time as we will be executing that command after pushing the code and you won't have to write that !? Obviously, you guys would have thought about this but I just wanted to know why it can't happen that way

[cchaos]

Hi @hetanthakkar1 We understand it's a slow manual process for reviewing community PR's and we appreciate your patience with us as we juggle maintenance of the repo alongside our other Elastic duties. The CI builds, and triggering them, are completely permissions based and managed by our internal infrastructure team. Since community members don't have access to the builds, they also can't trigger them. Sorry, but it's not part of our control on that side.

[hetanthakkar]

@cchaos I get it. I didn't know these CI builds are something that is very permission-based and important. I thought CI build is like test commands! I really appreciate your reviews and have learnt a lot while contributing. Thank you!

[thompsongl]

jenkins test this

[kibanamachine]

Preview documentation changes for this PR: https://eui.elastic.co/pr_4714/