Enhance performance of finding command to execute about mutgos_server

[zelerin]

Starting work on this.

[zelerin]

Reversing the order of relatively expensive security checks on actions themselves (do them after seeing if the action matches) plus allowing an already normalized (lowercase) string to be taken in for searching (rather than converting it to lowercase per action check) yielded a tiny bit of improvement - it takes less microseconds on an already microsecond level operation. I'm going to stop here with this sort of optimization mostly because we need a much more comprehensive database to better understand the bottlenecks. Anything done now is just conjecture.

Looking at log timestamps, the whole operation of finding an action, verifying security, and calling the 'launch angelscript process' method is actually very quick (microseconds). The AngelScript execution is also very fast. The slowness appears to be coming from the comm subsystem.

My original design called for it to be single threaded for simplicity, but to allow multiple comm interfaces (websocket, socket, and anything else someone implements) to be active at once, which basically meant polling each one in turn. During polling, it handles new connections, incoming data, and outgoing data. I had it set to poll every 1/4 second. Changing it to what I think is 1/10 of a second yielded a much more responsive system without taking up any noticeable CPU time when idle.

I have a feeling the polling design will need to be revisited one day, replaced by one thread per comm interface with a synchronized common area to interact with the rest of the system; this will make it extremely responsive. In reality, it would not be a big deal to switch it over, but I consider it lower priority at this time and prefer to work on functionality people would notice.

I'm going to leave this open for a bit longer in case I come up with a better idea, and if not, will check in what I have and close the issue.