Whitelist exploit fix and SQL crash fix

Updated the battery item with a better hold offset. This item needs to
be changed soon however, due to the model being used for the 5.56 ammo
tin (which fits the model better, as it is an actual ammo tin model)

Shifted the whitelist check to another part of the code, this means new
players can create an account before being notified and kicked for not
being on the whitelist. Previously, players could "hijack" accounts once
they were accepted into the whitelist via a forum if they were quick
enough. This will fix that problem as a player requesting for a
whitelisted name should already have an account on the game.

Removed some unnecessary code from account creation, creation of user
files (the save function uses "io_write" anyway so a new file is always
created).

Fixed the SQL insert query for new accounts to have default gender as
well, it was previously inserting no data which would cause a server
crash once this field is read.

Altered camera distance detection distances.

Added one line of code that completely changes how explosives can be
used in-game! Explosives will now only destroy one fort part at a time,
which makes base breaking harder. I do plan to make it always pick the
closest defence item soon as choosing the lowest ID can sometimes result
in undesired effects such as blowing up a defence that the user didn't
want to blow up.

Altered loot indexes some more, many weapons are rarer, especially those
in military and survivor spawns. Also lowered defence parts a lot as
well as keypads to make base building more challenging, which ties into
explosives too, these are more rare to make base breaking harder which
slows down overall gameplay for forts, players can now hold an area for
a longer period of time and there's less chance of it being broken while
they are offline for only a day.

Added 10 more spawn points to around the country areas (FC, TR, BC and
RC) and removed one from San Fierro as it was a bit too close to the
city.

Added some code to stop spawning at the same position as the last time a
player spawned.