Create Ban, CharacterBan, and IPBan objects, and create a new DB schema for bans against users.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Fix some issues with the schema and add enable and disable functions for all new ban objects.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Add banned properties to the User and EVECharacter classes, and restrict API calls in the api.core and api.proxy endpoints for banned users.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Add check for if a user is banned to the authentication routine, and deny logging in to users who are banned.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Add core/blacklist call for checking if a character or IP address has been banned.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Clean up the code, fix a bunch of typos, and remember to run the linter before committing.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Fix the banned property for characters, change the database fields to save storage space, and make the contains length requirements for core.blacklist more stringent.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Merge branch 'develop' into feature/blacklist

Conflicts:
	brave/core/api/core.py
Fix some issues with the banned functions in EVECharacter and User, and add search support for banned characters.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Merge branch 'develop' into feature/blacklist
Add banned support to the user search page.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Add ability to create bans, add ability to ban from account details page, fix some schema issues, and fix a ton of bugs.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Add support for the enabled fields when determining if a character or account is banned, fix the model a bit, and add __repr__ for the Ban objects.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Move the Ban stuff to it's own directory, and rename the ban collection to Bans.

Signed-off-by: Tyler O'Meara <Tyler@TylerOMeara.com>
Add CSRF protection

This requires that all effectful requests be done via ajax, which I
think is already true. If we wish to support normal forms, that is
possible, but will require slightly more work.

The "light" base template is not quite as light as before. Oh well.
'in' is not what I meant here
Require POST on effectful methods in group editor

Why I didn't do this originally, I'm not sure.

Also, TIL, if you use __lookup__, whatever you return will be treated
like a Controller, regardless of whether it actually is or not.
Do admin searches as GETs
Clean up dead JS
Merge pull request #248 from eve-val/fix-group-requests

Require POST on effectful methods in group editor