Per-frame GC Allocation when using HDRP Lens Flare Post Process Effect

How to reproduce:

1. Create and open a new 3D HDRP Sample Template
2. Open Profiler (Window → Analysis → Profiler)
3. Enable Deep Profile and Call Stack in the Profiler
4. Enter Play Mode
5. Record, and then press on any frame in the Profiler
6. Search for GC.Alloc in searchbar
7. Select any GC.Alloc in the Hierarchy
8. Change ‘No Details’ to 'Calls' in the Profiler
9. Observe the 'Calls From' section in the Profiler

Expected result: No GC.Alloc calls are made by ‘HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass()'
Actual result: One of the GC.Alloc calls are made by 'HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass()’

Reproducible in: 2023.3.0b1, 6000.0.60f1, 6000.2.8f1, 6000.3.0a1
Not reproducible in: 2023.3.0a19

Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested

Note: The Call allocates ~152 B each frame