Management (arbiter) permissions

[vintprox]

I'd like to introduce proof-of-concept NsMgmt model. There is so much to come up with permissions, but it will be good to have something simple in the end. So, NS Manager is title that user bears when they get all permissions to manage NonStory settings for guild or separate channels. Also, NS Management can solve disputes regarding questionnaires with override commands given to them, force lesser countdown and disciplinary means to apply on players.
NSM is bound to NsUser model, which makes easier migration of rights for them, if they suddenly decide to switch accounts (described in #3).

[vintprox]

As per #9, there will be few changes in models. They include renaming "channel" abstraction to "room" and "guild" to "server", allowing broader chat clients coverage.

ns_mgmt

Indexes:

• id, PRIMARY
• user_id + server_id, UNIQUE
• user_id + room_id, UNIQUE

user_id	server_id	room_id	id	(comment)
1	6	-	100	OK. User 1 is managing server 6 now
1	6	-	.	ERROR! Record with user 1 and server 6 cannot repeat
2	6	-	101	OK. User 2 is managing server 6 now
1	7	-	102	OK. User 1 is managing server 7 now
1	-	12	103	OK. User 1 is managing room 12 now
1	-	12	.	ERROR! Record with user 1 and room 12 cannot repeat
2	-	12	104	OK. User 2 is managing room 12 now
-	6	17	105	OK. Room 17 in server 6 is marked for NS Management
-	6	12	.	ERROR! Cannot mark two rooms for NS Management per one server