changes is sing_in_valid, base.jinja2, develop_login and develop_signup, and home.jinja2

changes in sign_in_valid.js
- commented some unnecessary alerts
- added function to support login from login page, without regexp
checkings

changes in base.jinja2 and develop_login.jinja2
- cleaning some unnecessary js files
- added some id's to login form, to support password hashing

changes in develop_signup.jinja2
- added value field, to some fields, that will be filled in with user
data if user form submit fails

changes in home.jinja2
- moved js file to base.jinja2
update regarding login/signup/add_user views in views.py

changes in views.py
- updated login_post:
- - - removed broken check, added the right one

- updated signup:
- - - removed direct access to dictionary keys, now it uses get method,
and less error prone
- - - right method now is used to check if user with given login and
email exists
- - - getting keys from request params is more secure, now only
hardcoded fields will get in user_details dict
- - - returning user inputted data, if js fails and not all fields are
filled in (role and status id's are removed from this response)

- updated add_user_post:
- - - added renderer, for case when user with given login or email
exists to return a message, but it is not used in template
- - - fixed check for existing users
- - - fixed error when we couldn't add a user because password field
was not supplied