Reduce Shibboleth column length to 255 characters

This is required because MySQL doesn't support indexes on tables larger than 767 bytes.
(See http://dev.mysql.com/doc/refman/5.5/en/innodb-restrictions.html for documentation on that).

The current limit of 1024 was arbitrary anyways - according to http://www.switch.ch/aai/support/serviceproviders/persistentid.html , the real limit is 2036 characters.
This change fixes #390.
What we should really do - and this seems to be pondered by Shibboleth protocol designers anyways - is to hash the persistent ID, and to index over that.
If needed, we can still store the original long ID in the database.
Added javascript code to pass the information of the `window.performance.timing`
object to requestlog 500ms after the load event is fired.
Added option in `adhocracy.ini` to activate this monitor
`adhocracy.monitor_page_performance`
Activated the new code with the option in the hhu.cfg
Merge pull request #392 from phihag/fix-issue-390-shibboleth-id-length

Reduce Shibboleth column length to 255 characters
Add treatments (for A-B tests etc.)

Treatments allow administrators to assign numerous users with badges.
In order to select the users that should apply, the administrator selects them by badges themselves.
The admin can then assign automatically generated treatment badges to these users.
Among each group the treatment badges are assigned randomly, but with the same amount for each treatment badge.

For example, possible source badges may be:

* Party members (10 users)
* Non-party members (21 users)

The administrator could then proceed to create a treatment "first-experiment" that could assign the users as follows:

* 5 party members get stuffed in group A and B each
* 10 non-party members get stuffed in group A, and 11 in group B.

Of course, this is only useful if we do more with the badges afterwards, for example use them to selectively send more/less/different emails via the mass messaging service, or different presets (hhucn/adhocracy.hhu_theme#121).
In the future, we could also add additional badge behaviors, like color schemes, font sizes, number of interface components, etc.

See hhucn/adhocracy.hhu_theme#110 for details on the big picture.
i18n: extract new messages
i18n: New german translations
Merge pull request #397 from carschroeder/new-german-translations-23may

New german translation
Fix typo and simplify treatments
Merge pull request #396 from phihag/treatments

Add treatments (for A-B tests etc.)
Changed the timout after that the navigation timing info is send to 10ms.
Changed the onLoad object from document to window, on some browsers the load event is only on window object fired.
Simplified the ajax send request for the navigation timing.
Remove unecessary parameter.
Merge branch 'record-navigation-timings' into develop

Closes PR #393

Conflicts:
	src/adhocracy/templates/root.html
Add option 'adhocracy.monitor_pager_clicks'.

Will be used to (de)activate monitoring of pager clicks.
Fix User.find_by_email function

Remove redundant and incorrect filter.
Determine default sort order centrally

Currently, the default sort order of proposal dialogs is set in the proposal controller.
Instead, it should be set by the pager itself, since there are multiple ways to include pagers.
This prepares a common infrastructure for solr and database-based sorts.
Activate controversy sorting in Solr-based sorts

We overlooked this; controversy has only been activated for database-based pagers.
Fixes hhucn/adhocracy#299
Unify Solr/database sorting

Currently, the user profile setting of the default proposal sort order has no effect on database pagers.
Make database pagers and solr pagers share some of the same data sources.
Fixes hhucn/adhocracy.hhu_theme#298
Merge remote branch 'origin/develop' into develop
Fix secret generation in config file (fixes #398)