Order version numbers to match the generation stack (oldest at bottom, newest on top)

Reported by a user via support. Current behavior: when multiple generations of a song stack in the list, the newest gen appears at the top, but the version numbers run the other way (v1 sits above v2, etc.). So the numbering and the visual stacking order disagree. Requested behavior: make the version numbers follow the stack order. Since v1 is the first generation created, it should sit at the bottom, with v2 above it, v3 above that, and so on, so the newest version is both on top and the highest number. Why it matters: right now the ascending version numbers read top-to-bottom while the gens stack bottom-to-top, which feels backwards and makes it harder to track which version is which during long generation sessions (this user ran 26+ gens on a single song). Aligning the two would make the version history easier to scan at a glance.