Remove sp_QuickieStore wait-stats per-interval TOP (5) pre-filter

The CROSS APPLY that joined to sys.query_store_wait_stats had:

    SELECT TOP (5) qsws.*
    FROM sys.query_store_wait_stats AS qsws
    WHERE qsws.runtime_stats_interval_id = qsrs.runtime_stats_interval_id
    AND   qsws.plan_id = qsrs.plan_id
    ...
    ORDER BY qsws.avg_query_wait_time_ms DESC

so for each (interval, plan) it kept only the 5 wait categories with
the highest per-interval avg wait time and discarded the rest. The
outer query then GROUP BYs (plan_id, wait_category_desc) and sums
across intervals. The net effect: a wait category ranked 6+ in one
interval but present in another silently loses the first interval's
contribution, making the same plan's totals inconsistent run-to-run
depending on which intervals it executed in.

Removed the TOP (and the now-unused ORDER BY) so every captured wait
category contributes to the outer aggregation. QS caps wait
categories to a small set per (interval, plan), so removing the TOP
does not blow up row counts.

Verified sp_QuickieStore installs clean and runs without error
against PerformanceMonitor on SQL Server 2022 with @wait_filter.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: erikdarlingdata

sp_QuickieStore/sp_QuickieStore.sql

@@ -10863,15 +10863,24 @@ FROM
     FROM #query_store_runtime_stats AS qsrs
     CROSS APPLY
     (
-        SELECT TOP (5)
+        /*
+        Pull every wait category captured for this (interval, plan).
+        The previous TOP (5) ORDER BY avg_query_wait_time_ms DESC here
+        dropped wait categories ranked 6+ per interval before the outer
+        GROUP BY ran, so a category that was (say) 6th worst in one
+        interval but 2nd worst in another would silently have the first
+        interval''s contribution missing from its totals. The outer
+        aggregation groups by (plan_id, wait_category_desc) and the
+        number of wait categories per interval is capped by QS at a
+        small set, so removing the TOP does not explode row counts.
+        */
+        SELECT
             qsws.*
         FROM ' + @database_name_quoted + N'.sys.query_store_wait_stats AS qsws
         WHERE qsws.runtime_stats_interval_id = qsrs.runtime_stats_interval_id
         AND   qsws.plan_id = qsrs.plan_id
         AND   qsws.wait_category > 0
         AND   qsws.min_query_wait_time_ms > 0
-        ORDER BY
-            qsws.avg_query_wait_time_ms DESC
     ) AS qsws
     WHERE qsrs.database_id = @database_id
 ) AS qsws_with_lasts