feat(UI): add iteration config for item group debug spawn test

[OrenAudeles]

Checklist

Required

• I wrote the PR title in conventional commit format.
• I ran the code formatter.
• I linked any relevant issues using github keyword syntax so it can be closed automatically.
• I have committed my changes to new branch that isn't main so it won't cause conflict when updating main branch later.

Purpose of change

When testing item distributions in item groups we don't always need to check 100 or 1000 iterations of item spawning. Making it configurable seems like the best compromise to match user desire by allowing options for how accurate they want to be while testing an item group's spawns.

Compromise for #5033 and #5872

Describe the solution

Adds an additional picker UI for how many iterations to run while testing item group spawns. Provides logarithmic progression options: 10, 100, 1000, 10000. More options can be added, or it can be changed to a text input, in a future PR if these options are not satisfactory.

Describe alternatives you've considered

I'd like to make it so we don't need to spawn items at all, even temporary items, and make it purely mathematical. Pick an item group, and then it calculates the chance of an item to spawn as if there were infinite iterations.

Testing

Tested multiple item groups with multiple iteration selections, including invalid / exit selection. Works as expected

Additional context

Future work / idea:

Items that can spawn with some variation, such as UPS spawning with differing charge take up multiple lines in the results list. Future work would probably be to make a collapsible list for those so the root level of the results list would have count of item type and expanding would show count of item type spawn values.

1x UPS (N / 1000)
1x UPS (M / 1000)
1x UPS (J / 1000)

would become

3x UPS [>]

and expand to

3x UPS [V]
- 1x UPS (N / 1000)
- 1x UPS (M / 1000)
- 1x UPS (J / 1000)

[scarf005]

i hate how our choice API returns index aaahhhhh

[OrenAudeles]

i hate how our choice API returns index aaahhhhh

yeah. I think it's pretty useful in a lot of cases, but sometimes it'd be useful to have some other result type. I'd really dislike having to convert back from a string to an int/size_t to get the number of iterations in this case.

[chaosvolt]