Adminotech: Profiling + MumblePlugin fixes + Tunda core camera fixes

<b>MumblePlugin</b>

* More sensible default settings for first time users/users who have not used the config wizard yet. Enables voice activity as the default transmission mode and puts more sensible defaults for VAD min/max so there is potentially less to config.
* Implemented selecting input device, before just picked the first device which was not very good for PCs that had multiple input devices.
* Apply certain settings automatically so user does not have to press apply to hear/see the effect.
* Fix resizing of audio wizard for mac.

---

<b>Camera Applications</b>

* For a client that is connected to a server we had 2 scenes running and 2 freecam apps. This took a 1% hit even if no free cams were apparently active. This is because the empty default 'TundraServer' scene only had freecam entity and it thought the camera is active even if the scene was not visible. This meant 2 times the current mainloop FPS (both scenes scripts) spam to its Update function that had some perf impact, especially since the two scripts were not even doing anything I decided to remove this "load".
* Also fixes so you cam move the freecam once you have pressed 'Locate' in scene editors right click context menu.
* Fixes so that no freecam ent is created and the script is not spinned for nothing when Tundra is headless.
* You might also think this is somewhat a micro optimization but I say ~10 msec total per second doing nothing (when no free cams were not active) was unwanted! :)

Please comment if you think this commit will break some scenarios with cameras! Only thing I am aware of is that when you disconnect the "TundraClient" scene, the camera app in "TundraServer" is not activated. There is currently no signal in Tundra so that this could be fixed. A emit SceneActivated(name/ptr) would be needed!

---

<b>Script Profiling</b>

New overloadable function in IScriptInstance that returns map of debug data. Profiler shows this information in a new 'Scripts' tab. This shows various info about the object tree of the script, easy to read if scripts are leaking mem as shows deltas for changes and totals for objects. Python scripts atm do not return any debug data, this has to be implemented if it is desired (and handled in profiler if the return data map has different keys).

This is the initial script profiling that we can do easily. We can add more information to the dump functions in the classes that implement IScriptInterface and to the ui when we want. I found this pretty useful already and found memory leaks from my scripts. You can leave the profiler open and do actions that your script handles, over time you see that object count grows. For well behaved scripts you can see it might preserve objects but after some time carbage collector removes them from the object tree.

* Follows the conventions in profiler window class: no update if not visible, no update if tab is not selected etc.
* Minimizes rendering updates for qt by not updating text string if they have not changed.
* Cleans dead entity/component rows from the UI.
* Updates all values to refrect the scene at 1000 msec intervals.
* Shows delta changes in parenthesis in all data cells eg. "800 (+3)"

Example screenshot from client with scenes/Avatar/scene.txml (http://dl.dropbox.com/u/3589544/profiler-scripts.png)

![Screenshot](http://dl.dropbox.com/u/3589544/profiler-scripts.png)