When using apply to children flag in repo group permission
change prompt, RhodeCode only applied this to user groups if
repository was private. Only thing that shouldn't be allowed is
to change the DEFAULT user permission when repository is private.

Repository groups: super admin shouldn't have the permission set
when he creates a group. Super admins anyway can edit groups even without
explicit permissions set

managing users groups enforce permissions checks.
User needs at least a read permissions on usergroup to be able
to assign it somewhere.

- Manage User’s Groups: create, delete, rename, add/remove users inside.
by user group admin.
In this case, a user's group can be owned by several people thru an owner user's group.

Some refactoring of naming, permission handling logic.
- remove some code duplicity as well as inconsistent naming

fixed issue with renaming repos group together with changing parents with multiple nested trees
added regresion tests for such cases

fixed issue with renaming repos group together with changing parents with multiple nested trees
added regresion tests for such cases

further cleanup of UsersGroup

Renaming some names ... but trying not to change API or database scheme.

"Users groups" is grammatically incorrect English - rename to "user groups"

- and same story with "repositories groups"

This will only change the user facing texts. Names of files, modules, functions
and variables should be changed too.

Group management delegation:
this allows users to become an admin of groups
a group admin can manage a group, change it's name
or permissions. A group admin can create child group
only within a group he is an admin off.

Top-level group can be only created by super admins

deleting a group now does same archive operation like deleting repositories. Improve prompt that show number of repos that will
be archived together with a group.

Permissions on group can be set in recursive mode setting defined permission to all children
- more explicit permissions
- fixes for empty values in permission form

Added form for controlling mercurial extensions
added hggit also for future

Added functional test create repo with a group
- unified calling Session in tests

utils/conf
- created temporary utils2
- made config.conf for storing some configurations
- fixed some dependency import problems
- code cleanup
- rc-extensions now properly work for celery

fixes issue #366 setting null on parent_group didn't propagate to actually db field.
- added relevant test for this

#227 Initial version of repository groups permissions system
- implemented none/read/write/admin permissions for groups
- wrote more tests for permissions, and new permissions groups
- a lot of code garden, splitted logic into proper models
- permissions on groups doesn't propagate yet to repositories
- deprecated some methods on api for managing permissions on
repositories for users, and users groups

garden
- unified logging formatting to use only %

fixes #288
- added group management into non admin repo settings form
- fixes also issues with groups after API codes merge
- all tests passes ok.

Added friendly message about removing a group that still contains subgroups.
Fixed option to remove a group that is not in filesystem (ex. someone deleted it intentionally on filesystem) in this case RhodeCode will simply just throw an error message saying this group cannot be deleted.

implements #226 repo groups available by path
fixes #259 Groups with the same name but with different parent group

#47 added editing of groups, and moving them between. Added check constraint for groups
to prevent of loops

#47 implemented Adding of new repo_groups+forms+validators. Fixed sorting of repo groups by main names in multiple locations. Removed some unneeded calls to self.sa for exchange to .query() methods.
Added new db unique key for Group