fix: [M3-6668] Broken K8 node pool infinite scrolling

[abailly-akamai]

## Description 📝

The scrollableAncestor="window" prop on the Waypoint instance was breaking the infinite scrolling for the node pools on a K8 cluster detail. From what I can understand and read, the prop is responsible for:

A custom ancestor to determine if the target is visible in it. This is useful in cases where you do not want the immediate scrollable ancestor to be the container. For example, when your target is in a div that has overflow auto but you are detecting onEnter based on the window.

Which we are not doing at all since our handler is based on a count of node pools.

Removing this prop fixes the issue (loads the next 25 node pools on scroll) and does not appear to introduce any other regression.

How to test 🧪

1. Pull code locally, and create 10 node pools on a given k8 cluster (no need to test with 25, we just want to test what happens when scrolling past the vertical viewport)
2. Modify the NodePoolsDisplay count on the default state to 5 so Waypoint can trigger earlier
3. Confirm you get all 10 node pools displayed once scrolling down (you may not see any loading state but all should be present almost instantly once scrolling down)