Temporary self de-opping

Patch below adds an @mortal command for this. (I did try a flag that negates Wizard() / Royalty() checks in the hardcode first, but a lot of stuff checks for the presence of the flags rather than using those, and softcode checks use hasflag(), so I decided against it.) @mortal <obj> replaces it Wizard and Royalty flags with Mortal_Wizard and Mortal_Royalty, respectively, and @mortal/wizard <obj> or @mortal/royalty <obj> restore them. Not sure if it's the best way to do it, but it seems to work OK, from the testing I've done.

Replying to KimikoMuffin:

My idea is for a flag (say, DE-ADMIN(d), or NOT-STAFF(n), or OFF-DUTY(f), or something not currently used by player-flags) which allows admins to temporarily "disable" their ability to use wiz/roy commands (@pcreate, seeing dbrefs and attributes, etc), and re-enable it at will, sort of analogous to a registered channel operator on IRC having the ability to remove and add op status to themselves in a particular channel. This wouldn't affect objects they own -- the "code wizard" could set it on themselves without breaking wiz-objects they own that are @set Wiz in room #2, for instance -- except insofar as they wouldn't be able to @force Wiz objects, say. Without having to login God, @set someone !wiz, and then re-@set them Wiz (which *would* break the wiz-objects in room #2). My reasoning for this is so that staffers can be off-duty in more than just name only. Especially if they find that they're getting angry and want to remove temptations before it's too late (I know what I'm talking about here). Yeah, it won't stop someone who's really determined to fly off the handle, but it'll just be ... another option, I guess.

Built against 1.8.3p5, hence the changes to src/SWITCHES