asymmetrical tiebreaker test with mapsBreak false
ffa message should not reveal inner workings
small groupstage refactor to reduce side-effects in complicated function
idString for TieBreaker
TieBreaker: ensure posByGroup is ascending in seed
TieBreaker: ensure border element cluster is pushed into R1 breaker
tiebreaker: better names for readability + avoid clashing and confusion in file-scope
factor out R2 generation in hope that it can be done for score function
TieBreaker::unscorable