Refactor the new User class to PlanningPokerUser

Now it won't conflict with the original user class in core.

Submitted by: sfmailand (primary), ajthompson (one tiny bugfix in the refactor)