Correlations: Refactor Correlations page for RTK Query

In response to https://github.com/grafana/grafana/pull/113803/files/7c52ba7e11e36d841a72438ead7a5fe18971e8d5#r2671378910 > In general, I'm not sure adapting the RTK Query implementation to support the legacy imperative fetchCorrelations pattern is the right direction. Since RTK Query is declarative (data fetches automatically based on hook params + cache invalidation), while useAsyncFn is imperative (you call a function to fetch), the cleaner approach would be to refactor CorrelationsPage to be data-driven and have the legacy path adapt to that - not the other way around. Migration to app platform meant using generated RTK query hooks to populate data. This brings in data differently than how the page was originally built. At the time, our primary focus was a successful migration, not building this page to perfectly handle the new approach. However, refactoring how data is fetched will clean this page up quite a bit.