Fix logging when we destroy a round (LoadBalancer)

[adamPetho]

Addresses: #12585 (comment)

Why is this so important for me?

Because in case there is an issue in the backend and we need to investigate it, more or less the logs are our only weapon.
If we cannot trust the logs or the logs are inaccurate, the investigation becomes much harder.

master produces logs like this:

2024-03-01 11:51:57.989 [71] INFO	Arena.CreateRoundsAsync (540)	Destroyed round with 360 inputs. Threshold: 450

This is NOT urgent to deploy.

[molnard]

LGTM

[turbolay]

Just a note, it is not detailed in OP's description, but this PR also fixes a potential problem where the roundDestroyerThreshold was based on Config and not roundParameters, so if for some reason a round had a different MinInput than what we had in the config, the roundDestroyerThreshold would've been non-sensical.

It didn't apply for the Delta PR specifically because RoundDestroyer doesn't apply for BlameRound

[molnard]

ACK