* If `kartvoterulechanges` is set to `Always`, the third option is always the opposite gametype, even if Encore is unlocked - that will now be present on the second option instead.
    * This is both for consistancy with having Encore inaccessible on your gamedata, and a response to community feedback.
* The `kartencore` cvar being turned on will now be reflected in gametype rule changes from Battle to Race. This plugs one last hole in its area of effect for Race tracks.

Increase maximum WAD and skin counts

See merge request !291

Thanks to Callmore's insistence on me sweeping through functions that
return -1 on error.

Don't sleep w/ fpscap 0 and vsync enabled

See merge request KartKrew/Kart-Public!294

Per @TehRealSalt's recommendation.

fix portal interp view positioning and camera reset

Closes #14 and #12

See merge request !293

Various fixes for 1.6

Closes #17, #15, and #11

See merge request !292

This time without spare slots, because I don't see shenanigans like
WAD_MUSIC happening with skin indices. Verified to work by saving a
replay with 139 skins as the 133th skin and playing it back a few times.
Shouldn't cause issues with netcode either because there are no SINT8s
handling skin indices.

Can be increased up to 255 safely, just not 256. 5 slots left for
shenanigans like Moe Mansion's WAD_MUSIC.

Update gfx.kart hash

CONS_Printf calls CON_Drawer during startup, thread
collision stuff.

Fixes some wild behavior when a lot of hole punching
requests are coming in.

This reverts commit 5ec44ba3, reversing
changes made to 4c5d69b7.

Doesn't prevent it from happening later if the rules weren't successfully fetched, though.

Notably caused by a difference in behaviour between Software and GL that was already resynchronised in the 2.2 codebase.

Seems to be a regression in internal too. Requires more analysis on behaviour in the 2.2 engine, but essential for maintaining compatibility in 2.1 (such as with Opulence wobbly carpet).

- `cv_masterserver` - Replaces a hack checking for the original SRB2 MS addres every time, and additionally catches those who tested an early version of the http MS.
- `cv_usegamma` - This was previously WAY too easy to accidentially change. This way, a user who has had this accidentially happen will automatically return to baseline.

I originally wrote a ridiculous attempt at reimplementing the existing value rollaround. For one reason or another, that sidesteps net transmission. Let's just avoid all those hacks and limit our influence to changing the maximum allowed range.

Doesn't affect the conditions that allow entry -- just avoids pointlessly resetting the map if it occurs during the period where literally nothing can happen.

v1.4 prep

See merge request KartKrew/Kart!631