Note: this is currently only deployed on staging. Use OTTD_COORDINATOR_CS="coordinator.openttd.org:4976" OTTD_STUN_CS="stun.staging.openttd.org:4975" to test this PR.

Motivation / Problem

With the removal of the UDP packets in lieu of the Game Coordinator listing, the ability to get the names for unknown NewGRFs for a server was lost.

Description

Introduce a new version for the Game Info packet that allows to specify the way the NewGRFs are serialized. This could be only GRF ID + MD5 checksum, GRF ID + MD5 checksum + name, or an index into a lookup table (more details later). For clients requesting information from a server, the names of the NewGRFs will automatically be sent.
Updates of a game server to the Game Coordinator will not send the names, except for the first registration of that game.

A new version of the Game Coordinator protocol was added so the Game Coordinator can provide a lookup table for the NewGRF ID + MD5 checksum + name for the NewGRFs in the listing. Upon further requests for the listing, in the same connection with the Game Coordinator, only minimal updates for the lookup table need to be sent.

Assuming about 500 unique NewGRFs used by all the servers combined, and 3000 server-NewGRF combinations this will save about 25 kB for the initial listing and 45 kB for subsequent listings.

Saving 3000*16 bytes = 48 kB in the listing.
    replacing GRF ID + MD5 checksum with index reduces 16 bytes per server-NewGRF combination.
Adding at most 500*(4+16+80) = 50 kB in the lookup table.
   GRF ID + MD5 checksum + maximum length of GRF name.
However, the average number characters of unique BaNaNaS NewGRF names is about 20.5 characters long (21.5 with '\0'),
so it costs closer to 21-25 kB in the first lookup table update. Updates after that only need to send new NewGRFs, 
which will usually 0 NewGRFs or at most a few NewGRFs.

Limitations

• Slightly more load for the Game Coordinator.
• Clients get names of NewGRFs that they might not need as they have the NewGRF locally.

Checklist for review

Some things are not automated, and forgotten often. This list is a reminder for the reviewers.

• The bug fix is important enough to be backported? (label: 'backport requested')
• This PR affects the save game format? (label 'savegame upgrade')
• This PR affects the GS/AI API? (label 'needs review: Script API')
  • ai_changelog.hpp, gs_changelog.hpp need updating.
  • The compatibility wrappers (compat_*.nut) need updating.
• This PR affects the NewGRF API? (label 'needs review: NewGRF')
  • newgrf_debug_data.h may need updating.
  • PR must be added to API tracker