Player trails

[Warfork]

Client:

• cg_trailsPlayers (show player trails):
  "0" = Disabled
  "1" = Enabled (default)

• cg_trailsTeam (show team trails):
  "0" = Disabled
  "1" = Both teams (default)
  "2" = Current team
  "3" = Enemy team

• cg_trailsSpectator (Spectator mode\Warfork TV):
  "0" = Disabled
  "1" = Enabled (default)

• cg_trailsAlpha to set the opacity.

• cg_trailsSize to set the size.

• cg_trailsColorPLAYERS to set player trails colors. Default: "255 157 0"

• cg_trailsColorALPHA to set "Forbidden" team trail colors. Default: "235 140 138"

• cg_trailColorsBETA to set "Icy" team trails colors. Default: "141 183 224"

Server:

• The minimum speed for a trail to display will be set by the gametype, if it is not specified then it will be 1000+ UPS.
• Gametypes can enforce cg_trailsPlayers, cg_trailsTeam, and cg_trailsSpectator settings.

Reasons for gametype scripts controlling these settings: #192 by @Gelmo

Issue(s) with: 7b3bab2 raised by @Gelmo

https://streamable.com/byt303

"Here's an example. First, it's just me and my trail is mostly solid with minimal sparks. Then I add 7 bots. Then I move again and you can see my trail is more fragmented and there are more sparks. I then remove the bots, wait for them to leave, move again, and my trail is back to being less fragmented and having less sparks. You'll also notice, after adding bots, that my trail starts "okay" and gets worse as more bots spawn in and start moving. So the more particles that are being drawn, the less solid a player's trail can be. Unless MAX_PARTICLES is raised to a point where it's not a factor. Since MAX_PARTICLES is used in cg_effects for other effects, maybe a new variable should be introduced like MAX_TRAILPARTICLES. Otherwise, having player trails enabled also has an impact on the existing non-trail particles" @Gelmo

#191
#190