Fix compiler warnings for freeing (const char*)

pValidName is a const char*, so under alternative mux allocators (yes,
yes I know) this can produce warnings when things try to free memory
using it.

The original value of pValidName is not freed, as it really is (const
char*), and munge_space allocates a new LBUF for its munging.  s_Name
duplicates its input, so really all that needs freeing is the output of
munge_space, which the original code did.  It's the casting from char*
to const char* that's problematic because it makes the free (via
pValidName) illegal under more direct allocator methods.

c.f. line 379 under the TYPE_PLAYER case, which handles this right--
using buff just like in this patch.
use BLIND on rooms to really silence messages

* Covers X goes home.
* Covers connected/disconnected/partially disconnected.
* Works even with REALITY_LEVELS configured.

This is for quiet rooms and character freezers, and allegedly breaks
other games that use BLIND rooms for some other purpose.

Based on 37c8fcf06b34f57ad9f06b060acdcbe37521cc32 but with changes to
REALITY_LEVELS support.
Try 64000 char lbufs for the Reach.
Change the Boyer-Moore-Horspool implementation to account for larger LBUF_SIZE
Cause command lookups on master room objects to consider parents
Change bare 'think' to not alter idle() time
Add a basic .gitignore file