Fix JWT issues when changing servers

[AminArria]

Motivation

Currently in a client if you get a JWT for one server and then change servers the client will try to re-use that same JWT. In the case of Brazil and Europe it would work cause currently they share gateway server, but if you go from localhost to Europe then you face problems. Essentially when you try to go across gateway servers and have a JWT in your client

Summary of changes

• Extend SelectServerIP to change the gateway server to use and the PlayerPrefs key where the JWT for that server is stored
  • Now CUSTOM expects 2 IPs, arena and server in a format arena_ip gateway_ip (notice the space, also gateway needs the http/https part)
• Extend ServerUtils to use the new information in SelectServerIP
• Small cleanup of unneeded IP prefabs

How has this been tested?

To test this play across servers without clearing PlayerPrefs or app data

To test with Ngrok you will need to extend your configuration to be able to handle both tunnels. You can modify you ngrok config with ngrok config edit and putting

tunnels:
  arena:
    proto: http
    addr: 4000
  gateway:
    proto: http
    addr: 4001

And then you can do ngrok start --all

Checklist

• [x] I have tested the changes locally.
• [ ] I have tested the whole game after applying the changes, not only the affected areas.
• [ ] I self-reviewed the changes on GitHub, line by line.
• [ ] I have tested the changes in another devices.
  • [ ] Tested in iOS.
  • [ ] Tested in Android.
• [ ] This change requires new documentation.
  • [ ] Documentation has been added/updated.

[ncontinanza]

muted.mp4 I can't go through the title screen when setting the custom server, but when using the Brazil one it works fine.

@AminArria please explain in the log that the input should be ARENA_IP https://GATEWAY_IP

[tkz00]

muted.mp4

I can't go through the title screen when setting the custom server, but when using the Brazil one it works fine.

This was because https:// was missing from the second URL