[BUG] spectator-v5 doesn't return full perkIds
Bug Description
When calling the spectator-v5 endpoint, the perks->perkIds array inside participants only contains the main rune ID instead of the full list of perk IDs (including stat runes).
Problem Description
Previously, the perks->perkIds field contained all selected runes (primary tree, secondary tree, and stat runes). Currently, it only returns a single ID (the keystone rune). This regression breaks downstream logic that depends on having the full rune setup.
Expected Result
The perks->perkIds array should include all runes chosen by the participant (keystone, other runes in the primary/secondary path, and stat shards).
Example:
"perkIds": [8112, 8126, 8138, 8135, 9111, 9104, 5008, 5002, 5003]
Actual Result
The API response only includes a single ID in perks->perkIds.
Example:
"perkIds": [8112]
This was done on purpose as noted on by Riot Auberaun but we definitely lacked communication from DevRel on this.