Feat: Auto Kick on login

[RyanYappert]

Attempts to address 6008s with some RPC machinery.

• Adds KickOnMultipleLogin, KickOnMultipleLoginTries, KickOnMultipleLoginTimer to the LoginServerSettings, fter NoOperationTimeOutTime. These default to false, 3, and 5000 (ms) respectively.
• Adds a new column to GameServerList.csv: LoginId. This is the ID of the login server associated with this channel. The login server has to have some credentials for authenticating the internal RPC routes, so it piggybacks on the gameserver auth that it runs alongside. This may change in the future.
  • Make sure to update your GameServerList!!! Otherwise your server will not launch properly.
• When logging in, if KickOnMultipleLogin is enabled, the login server attempts to kick any connected accounts that match the accountId that's joining. It'll do this KickOnMultipleLoginTries times, waiting KickOnMultipleLoginTimer milliseconds between each attempt. Only after failing the maximum number of times will it return the usual 6008 error.
  • Note that the client has limited patience, so the number of attempts and time between attempts should be small enough such that the client doesn't consider the login failed. At the same time, it must be long enough so that the other GameServers have enough time to actually handle the RPC command, which involves a DB lookup.

Checklist:

• The project compiles
• The PR targets develop branch

[pacampbell]

Should we make these nullable like I did with the modifier settings (so we can assign defaults for existing files)? The way our settings file works, it only generates new fields if the file doesn't exist. If it exists and the field is not present, it doesn't assign the default values we have in this file. Instead, it assigns the type default values (like 0 and false).

[RyanYappert]

Added a slightly different solution that doesn't require changing how we reference settings because of nullability.