Clear the active monster list after a player logs out

If the list wasn't cleared you'd see creatures for the person you were previously logged in as.
Added this IntelliJ version control config file
Updated a few old "appmobi" references to the new "intel.xdk" namespace
Introduced a facebook stub class that we will use when testing the app in the emulator

This stub makes no real calls to Facebook. Instead it returns prebuilt data. For example when the app asks for players it will always return the same list. It's hard-coded in the stub.
Always add the currently logged in player when starting a new monster. And he cannot be removed.

This required some structural changes. I was seeing wacky behavior when NewMonster extended the backbone Model class. Like, even though I was creating new instances, the player list wasn't being cleared. Weird. Anyway it really didn't need to be a backbone model at all since it's not a CRUD type entity with attributes that get persisted. It's just a home for the business logic involved in starting a new monster.
After creating a new monster the user will be sent directly to the canvas screen

And the new monster will be added to the active monsters collection so it shows up on the main menu without a server refresh.