First step in two-part process to rename directories to kallithea.
This first step is to change all references in the files where they refer
to the old directory name.

Imported some of the GPLv3'd changes from RhodeCode v2.2.5.

This imports changes between changesets 21af6c4eab3d and 6177597791c2 in
RhodeCode's original repository, including only changes to Python files and HTML.

RhodeCode clearly licensed its changes to these files under GPLv3
in their /LICENSE file, which states the following:
The Python code and integrated HTML are licensed under the GPLv3 license.

(See:
https://code.rhodecode.com/rhodecode/files/v2.2.5/LICENSE
or
http://web.archive.org/web/20140512193334/https://code.rhodecode.com/rhodecode/files/f3b123159901f15426d18e3dc395e8369f70ebe0/LICENSE
for an online copy of that LICENSE file)

Conservancy reviewed these changes and confirmed that they can be licensed as
a whole to the Kallithea project under GPLv3-only.

While some of the contents committed herein are clearly licensed
GPLv3-or-later, on the whole we must assume the are GPLv3-only, since the
statement above from RhodeCode indicates that they intend GPLv3-only as their
license, per GPLv3§14 and other relevant sections of GPLv3.

Fixed issues with how mysql handles float values. Caused gists with
expiration dates not work properly on mysql.

Add autoincrement for sqlite into Gist table.
Fixes some collision issues with gists after they got deleted

Add default for dashbord items and create default
settings in a sane way.

refactored url.resource to full definition of routes

- id -> gist_id

added alias configuration option for gists.
Used to generate nice looking urls for gists

Implemented simple gist functionality ref #530.

- creation of public/private gists with given lifetime
- rhodecode-gist CLI for quick gist creation

locking API returns objects instead of string messages.

- it's now possible to easily parse the output of lock functions

UserGroup on UserGroup permissions implementation.
- user group can have another usergroup assigned
- it's impossible to assign usergroup on the same usergroup

Added separate default permission for external_auth account
activation. This flag allows users to define separate option of how
activation of external_accounts should be performed.

invalidation: merge .invalidate and .set_valid as .test_and_set_valid

This simplifies the internal API and avoids leaking CacheInvalidation instances
and cache keys.

api: don't report invalidated cache_keys after invalidating a repo

The keys are an implementation detail and is never relevant outside RhodeCode
internals and should not be leaked.

fixed default permissions population during upgrades
- it often happen that introducing new permission
caused default permission to reset it's state to installation
default.
new version makes sure that only missing permissions are
created while leaving old defaults

- 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

invalidation: simplify get_prefix

str.split will always have a [0], and cache_key will always contain
repo_name=cache_args and the split will thus always return two elements

follow Python conventions for boolean values

True and False might be singletons and the "default" values for "boolean"
expressions, but "all" values in Python has a boolean value and should be
evaluated as such. Checking with 'is True' and 'is False' is thus confusing,
error prone and unnessarily complex.

If we anywhere rely and nullable boolean fields from the database layer and
don't want the null value to be treated as False then we should check
explicitly for null with 'is None'.

Switched handling of RhodeCode extra params in consistent way
- use only os.environ for both hg and git
- hacking ui objects was bad
- os.environ allows easier to call rhodecode hooks externally

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

fixes #762, LDAP and container created users are now activated based on
the registration settings in permissions

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

Update changeset cache should use non-cache version of repo if given attribute is empty, it's easier to controll how changesets are udpated
The quick update logic in base controller get's cached version and updates, while any other call will use non-cached version

further cleanup of UsersGroup

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

fixes #762, LDAP and container created users are now activated based on
the registration settings in permissions

git hook handler shouldn't ever use cache instances
- moved cache invalidation into finally block so we invalidate at latest possible stage
- added scm_instance_no_cache property to get non cached scm instances always

fixes for issue #731, update-repoinfo sometimes failed to update data when changesets
were initial commits

improved extraction of user from changeset when sending notification.
Fallback to repo owner if we cannot get the user

repository extra fields implementation
- verion bump to 1.6
- migrations

git hook handler shouldn't ever use cache instances
- moved cache invalidation into finally block so we invalidate at latest possible stage
- added scm_instance_no_cache property to get non cached scm instances always

filter out repo groups choices to only ones that you have write+ access to. Before it was read+ access and you got proper
error saying that you don't have write permissions to group to create repo in. Filtering out the read groups is less confusing for users.
ref #730

Return a list of invlidated keys on mark_for_invalidation func
- log.debug list of invalidated keys

fixes for issue #731, update-repoinfo sometimes failed to update data when changesets
were initial commits

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

improved extraction of user from changeset when sending notification.
Fallback to repo owner if we cannot get the user

Full IP restrictions enabled
- short cache query for IP for performance
- remove redundant logic
- some small css fixes for login form to better show IP restricted message

Added UserIpMap interface for allowed IP addresses and IP restriction access
ref #264 IP restriction for users and user groups

Default parameters are now also used for creating repos using API calls, and initial repo scanner
- added new parameters to API call to override defaults
- docs update
- repo_type is now optional as it's a part of defaults

Implemented better support for Wildcard queries
add username column to journal for caching logs after user deletion
added tests for admin journal
migrations

Implemented #379 defaults settings page for creation of repositories
- locking
- statistics, downloads
- repository type

implemented #663 Admin/permission: specify default repogroup perms
- added migration that adds new default permission for groups
- merged with patch from Vincent Caron

Added option to ini files for controlling full cache of VCS instances.
This can increase performance for huge repositories like 300K changesets

Cleaned the way cache keys are invalidated
should fix issue #504 RhodeCode is showing different
versions of README on different summary page loads

added caching layer into RSS/ATOM feeds
- updated code for new LimitedDiffContainers
- invalidate rss/atom cache keys on push
-

Update last_change from VCS data on request.
- lightweight dashboard shows now last_date also taken from db and it is fast !

Implemented permissions for writing to repo
groups. Now only write access to group allows to create a repostiory
within that group