Improve consistency around “match” vs “game”

[delucis]

There is still some work needed to make the framework fully consistent around using the term “match” to describe an instance of a specific game (see #709). Should we aim to get this done as part of 0.40.0?

• Database connectors (would require updating the various third-party connectors):

  • createGame method should be renamed createMatch

  • listGames method should be renamed listMatches

  Done in Improve match term consistency #806

• gameID → matchID

  • in React client

  • in plain JS client

  • in debug panel

  • in master

  • in server transport (cosmetic argument renaming)

• gameMetadata → matchMetadata

  • in React client

  • in plain JS client

  (This had in fact been done in Fix #703 - Use the term "match" in the API and Lobby #704, because the 0.40.0 docs have been updated to show matchMetadata, but I think I may have overwritten those changes when merging in the Typescript clients.)

• updateGameID → updateMatchID (plain JS client)

There may be some more I’ve missed, but I think that’s most of it.

[evandroabukamel]

Hey, @delucis , I'm working on that if you don't mind. I'm opening a PR.