Execute the prepared burst scenario (from SRVKP-9673) to test the hypothesis that Tekton Results may fail to store PipelineRuns during API latency spikes under high load. Before running the test, configure Tekton Results with aggressive persistence settings: `-completed_run_grace_period=1m` and `-store_deadline=1m`. These settings will make Tekton Results more prone to failing storage during API latency. The test will use a single namespace and will generate PipelineRuns according to the burst profile. Analyze the resulting `tekton_pipelines_controller_pipelinerun_total` metric and Tekton Results counts, looking for significant discrepancies during and after the burst, specifically focusing on whether TR drops PipelineRuns.