Renaming api's and creating helpers. Change password new sp usage.

1. Moving few reusable defines to constants.js. 
2. Earlier we were using usp_user_auth to get the password from DB, but this query is based on string(email)
Since we have the user ID, a new SP to retrieve pwd from user_id has been provided by Aragon. 
3. There have been lot of discussions on understanding the difference between an API and helpers, keeping future scale deployment model in mind we are modifying all the controllers for various actions like email validation, password management, device management to be part of sparkk login helpers.  And anything that returns a readable data as response is perceived as an API moving forward.

Testing with current change set:
1. Basic sanity tests for login moduel- namma auth
2. G+ Signup tested 

PS: Apologies for the out of context branch name, initially started with a different intention. 
Sure makes sense, will update it!

Sent from my iPhone

> On Sep 9, 2014, at 4:00 PM, frodo14 <notifications@github.com> wrote:
> 
> In node_modules/sparkk/defines/constants.js:
> 
> >  exports.DB_USER_TYPE_IS_REGULAR  = 1;
> >  exports.DB_USER_TYPE_IS_FACEBOOK = 2;
> >  exports.DB_USER_TYPE_IS_GOOGLE   = 3;
> >  exports.DB_USER_TYPE_IS_TWITTER  = 4;
> >  /*User Type Define End*/
> >  
> > +/*User Gender Define Begin*/
> > +DB_USER_GENDER_IS_MALE    = 1;
> > +DB_USER_GENDER_IS_FEMALE  = 2;
> > +DB_USER_GENDER_IS_NONE    = 3;
> > +
> > +exports.GENDER = {
> > +  'male'  : DB_USER_GENDER_IS_MALE,
> > +  'female': DB_USER_GENDER_IS_FEMALE,
> > +  'none'  : DB_USER_GENDER_IS_NONE  
> Since the values are already under "GENDER", I think we should name like this DB_USER_IS_MALE
> 
> —
> Reply to this email directly or view it on GitHub.