TeamTabs and PlayerTabs standardization

[SobakaPirat]

Is your feature request related to a problem? Please describe.
TeamTabs and PlayerTabs over the wikis have a lot in common and I believe they could be standardized.

Describe the solution you'd like
Modules should have this kind of functionality:

• Read current title and extract subpages
• Build tabs based on wiki config:
• • Default Subpages
• • Special Subpages
• • QueryLinks
• • Player/Team Subpages (for TeamTabs)
• Build year tabs
• Display tabs

Additional context
Сurrent modules functionality:

• Default Subpages
• Special Subpages (Tabs are displayed only if pages exist)
• Subpage DISPLAYTITLE (Team/Results -> Team: Results)
• Query links (TeamEarningsStats, Head to Head, Statistics)
• Year Tabs (Tabs for results/matches by year)

TeamTabs specific functionality:

• Player/Team Subpages (Tabs to separate Team Achievements/Members Achievements)
• SubTeams (Didn't find any use cases, but should make tabs for links like TeamName/Academy)

[hjpalpha]

imo very low prio

• existing modules aren't that bad
• lots of wiki specific stuff going on with these tabs
  • e.g. some wikis use /Matches while others use Played Matches (some use it differently between teams & players, some have an extra subpage for matches of players on the team)
• some of the requested features are not reasonable
  • fetching all subpages is not easily doable, would need a predefined list of pages to check ...
• the request for the queryLinks means we can not simply put the config in Module:Info, but have to make lots of custom modules...

[mbergen]

• the request for the queryLinks means we can not simply put the config in Module:Info, but have to make lots of custom modules...

We could define a format that allows to define a list of queryLinks in Module:Info?

[hjpalpha]

• the request for the queryLinks means we can not simply put the config in Module:Info, but have to make lots of custom modules...

We could define a format that allows to define a list of queryLinks in Module:Info?

i think the better solution would be to use String.interpolate

we couldn't use mw.uri.buildQueryString with that one though

mind it isn't just the base link that is different between wikis, the used params are too

maybe having a standardized h2h (new module & new form) first would be preferable
that way we wouldn't have to worry about wiki specifics when building the link