[WIP/Do not merge] Revamps bots, and adds the Bot call ability!

Grants the AI the ability to call bots!

How it works:
- The AI uses "Access Bot Control" verb to bring up a popup containing all of the bots within the AI's Z level.
- From here, the AI can learn its general location and what it is currently doing.
- The AI can remotely access a bot's interface using the "Interface" button.
- The AI selects "Call", which puts it in "Waypoint Mode".
- The AI then clicks a valid, unobstructed spot on the station.
- The designated bot then responds to the call and attempts to move to chosen waypoint.
- While the bot is responding to the AI's call, it is granted all-access to prevent the AI having to pre-open doors to clear a path.
- If the bot happens to be off, it will be turned on automatically. (if the bot is not EMP'ed or something)
- Hacked bots gain a warning symbol before the name.
- <B>Manually emagged bots do not show up on the panel at all.</B>

Patrolling enabled for floorbot and medibot! Both are now able to patrol the station, search for patients and hull breaches! Patrolling defaults to off for these types.

Poll justifying the continued effort for this project found here:
http://tgstation13.org/phpBB/viewtopic.php?f=15&t=418

Current bot panel - 
![screenshot 2014-06-06 18 26 44](https://cloud.githubusercontent.com/assets/4955510/3206986/1207ed76-edd2-11e3-8bce-6fa66dd3c5da.png)



<B>Remie Edit: Approved for use of Topic Procs</B>
"bot_type" is used for "send_status()" which requires a string. It is an input for a radio signal to interact with beacons and PDAs. (see in the PDA folder "radio.dm" and "cart.dm") In this code, it is currently only used for security robots ("secbot") type and MULEs ("mulebot") types, as there are only two signal filters for bots. The other filters will be added to this PR once I am done coding them.