RSS feed GUIDs are unstable when multi-architecture wheels arrive at different times

[ryanpetrello]

Summary

The GUID fix from #1374 (appending #timestamp to make rebuilds visible) causes feed readers to show duplicate entries when platform-specific wheels for the same (name, version, build_tag) arrive at different times.

Root cause

iter_releases() groups by (name_normalized, version) and annotates added_at=Max("file_added_at"). The GUID is link#pubdate.isoformat(). When a new architecture wheel is promoted (e.g., s390x arriving an hour after x86_64/aarch64/ppc64le), Max(file_added_at) shifts, producing a different GUID. Feed readers treat the new GUID as a new item.

Proposed fix

Replace the timestamp-based GUID fragment with a build-tag-based fragment. Use ArrayAgg("filename") in the query, extract PEP 427 build tags from wheel filenames in Python, and construct GUIDs like link#builds=1,2.

This makes GUIDs:

• Stable when additional platform wheels arrive for the same build tag
• Different when a genuine rebuild introduces a new build tag (the original RSS feeds show stale timestamps for rebuilt packages and have a low update limit #1374 requirement)