You manage an Azure SQL Database that serves an application generating thousands of unique ad-hoc queries per hour, most of which execute only once. After enabling Query Store with the default configuration, you notice the Query Store storage is filling rapidly and frequently switching to READ_ONLY mode, causing you to lose telemetry for the important, frequently-executed queries. You want to reduce the noise from single-use queries while continuing to capture meaningful, resource-intensive queries. What should you configure?