## Description The Community page currently triggers additional database queries for each published PC build when retrieving its components. This creates an N+1 query problem, where displaying 20 builds can require approximately 21 SQL queries. Optimize the backend to retrieve build components more efficiently, particularly as the number of published builds increases. ## Acceptance criteria - [ ] Remove the N+1 query pattern when fetching published builds. - [ ] Use batching, joins, or another suitable approach to reduce database queries. - [ ] Ensure all published builds still display their correct components. - [ ] Verify that database query counts remain low as the number of returned builds increases. ## Dependencies None.