feat: Add autoPlayed funtionality for TeamParticipants

[hjpalpha]

Summary

if |autoplayed=true is set in an opponent in the TeamParticipants template it enables a lookup in match2 data which player actually played in any (team) matches of the tournament the TeamParticipants is used for.

Funnily enough this implementation would make import from match2 data for players quite easy too.
So if we want/need this at a later date the changes for that are minimal.

fwiw importing all teams from a toruanemt with their players from match2 without specifying any teams/players is basically not a good idea with how TeamParticipants stuff is set up...

How did you test this change?

{{TeamParticipants|dev=hjp
	|{{Opponent|StreamerZone|autoplayed=true
		|players={{Persons
			|{{Person|sOs|role=captain}}
			|{{Person|Gerald}}
			|{{Person|LunaSea}}
			|{{Person|BabyMarine}}
			|{{Person|QuanTa}}
			|{{Person|Jumy}}
			|{{Person|NightMare}}
		}}
	}}
}}

on https://liquipedia.net/starcraft2/CranK_Gathers/Season_2

• if used above the prizepool or in section preview no autoPlayed is applied
• if used below prize pool autoPlayed is applied correctly

[Eetwalt]

couple of typos, otherwise looks good to me

[ElectricalBoy]

lgtm modulo typo

[mbergen]

Will this lead to issues with data cycles or mismatches?
Without the variables being stored (played=false) by the teamcard, the storage in the match will be bad, so importing that can cause issues.

[hjpalpha]

Will this lead to issues with data cycles or mismatches? Without the variables being stored (played=false) by the teamcard, the storage in the match will be bad, so importing that can cause issues.

the wikis this is (mostly) intended for (craft wikis) already store the players in match.match2opponents[X].match2players if they are set in a map even if they are not set in TC

Lua-Modules/lua/wikis/commons/MatchGroup/Input/Starcraft.lua

Line 272 in 7d0ba4c

function MapFunctions.getTeamMapPlayers(mapInput, opponent, opponentIndex)

we currently already use a very similar logic on sc, sc2 and stormgate (only real diff is that instead of parent we use stages input, but implementing that for the new TC we would need to pass more stuff into settings and you wouldn't want to have to enter that per opponent...)

additionally this functionality is to be enabled via a param (hence by default not enabled and not causing issues) and manual input always wins

[hjpalpha]

retested