Flowers are wrong in API

**Describe the bug**
Scorekeeper api shows the flowers weird/straight up wrong. They are labelled close and far and have the same data for both alliances. For example:

API:
- blue alliance:
```json
"closeFlower": ["RED_NECTAR", "POLLEN", "POLLEN", "POLLEN", "POLLEN", "RED_NECTAR"],
"farFlower": [],
```
- red alliance:
```json
"closeFlower": ["RED_NECTAR", "POLLEN", "POLLEN", "POLLEN", "POLLEN", "RED_NECTAR"],
"farFlower": [],
```
DB:
```json
"redAllianceFlower":["RED_NECTAR","POLLEN","POLLEN","POLLEN","POLLEN","RED_NECTAR"],
"scoringFlower":[],
"blueAllianceFlower":[],
"audienceFlower":["BLUE_NECTAR","POLLEN","POLLEN","POLLEN","RED_NECTAR","POLLEN","POLLEN","BLUE_NECTAR"]
````

**Expected behaviour**
The API returns the same values the DB has saved (all 4 flowers)

**Screenshots**
If applicable, add screenshots to help explain your problem.

Attachments are the DB (matchScore table as csv) and the API response

[API Response](https://github.com/user-attachments/files/32148851/response_1789234767570.json)
DB (matchScore table as csv)

```csv
matchId,alliance,scoreData
�e��d

**System info**
Windows 11, local scorekeeper v8.0.0-beta.2

Start by comparing the API Response attachment with the matchScore table data in the issue, focusing on how redAllianceFlower, blueAllianceFlower, scoringFlower, and audienceFlower are exposed for each alliance. Trace the scorekeeper API path that maps the saved score data into the response; done means the API returns all four saved flower values without duplicating or relabelling them.

Written by the indexing model from the issue text.