…ages

The lua shared functions lib now supports calling a hook
for when plugin data was parsed.
A bot now can hook custom code into some shared_functions library,
by implementing the functions.supplying for example: `fgcom.hooks.parsePluginData_afterParseIID = function(sid, iid) ... end`

Currently these are available:
- parsePluginData_afterParseIID(sid, iid)
  called when parsePluginData() received data for a given iid

- fgcom.hooks.parsePluginData_newClient(sid, iid)
  called when parsePluginData() detected that the client was not seen before.
  is called before any datas is parsed/added.

- fgcom.hooks.parsePluginData_updateKnownClient(sid, iid)
  called when parsePluginData() detected that the client was known.
  is called before any datas is parsed/updated.

- fgcom.hooks.parsePluginData_processedPacket(mumble_user, packtype, dataID_t)
  called after processing the packet, passing raw data

- fgcom.hooks.cleanupPluginData_entry(sid, iid)
  called when cleaning up an entry. return false to prevent the entry to be cleaned out.

-------------------------
Server/Statusbot:
Also this commit tries to prevent duplicate entries (#177).
make sure, the data structure has a type field default, and prevent nil value (#174)

fix #174
fix #177

fix #179

Also the test/fgcom-fakepilot bot was ammended:
- now also has a version number
- now utilizes fgcom.log() and .dbg() for output (giving timestamps)

- checkMissingPluginData(client, askForMissingDataAfter=30) added to fgcom-sharedFunctions
  - This will check for missing metadata.
  - If client is supplied, and askForMissingDataAfter is >0, it will emit a
    ICANHAZDATAPLZ packet to the client in question
  - It will return a table containing detected missing fields.
    So calling with client=nil can be used to just check for missing data.

- The status and recorder bot will now ask for data if it misses it for too long.

…ANHAZDATAPLZ query

…y the next choosen frequency is preannounced on the net

- FakePilotBot:
  - randomized start position globally (not locally around 0,0 anymore).
  - added optional --lat, --lon and --alt parameters to define a fixed start location.
  - fixed lat/lon mixed data in UPD_LOC packet.
  - fixed limiting/wrapping of lat/lon; it will wrap over correctly now.
    The bot thus now follows a great-circle path over the globe.

- loadTest tool:
  - changed call options. There are now 3 mandatory options (for the script itself).
  - options after the initial 3 ones are passed to the bot call directly.