remove dummy app

We're not supporting including leap_web as a gem right now.
move braintree initilializer into core

it needs APP_CONFIG to be loaded and was failing due to that.

Also this sets up some configuration options. They might only be needed if the billing engine is used but they should not be nested in there never the less.
backport bootstraps 3.2s list-inline

list-unstyled comes for free
Enable unblocking handles in identities tab

There's an identities tab now for admins that will allow unblocking blocked handles. It should be easy to expand for aliases and forwards and other types of actions such as editing.
make link_to_navigation more generic and reuse it

Use link_to_navigation for all important navigation items. It creates a link in a list item for use with bootstrap. It supports an :active flag and an :icon option in the html_options now. It also translates the label. This way it can be used in a lot of places as the generic navigation link.
create client certificates with generous not_before (fixes #5884)
list identities based on search only
Merge pull request #173 from azul/feature/unblock-handles

Allow admins to unblock handles
minor: remove dummy dependency in engine test_helpers

This was causing problems with zeus
stay on all tickets view when sorting (#5879)

When an admin sorted the tickets view in a different order it would take them to their own tickets list before
minor: cleanup some links

only submit the params that differ from the defaults
only use user ticket(s) path for real users
adopt ticket list test to new behaviour

We completely ingnore the user_id param for non admins now. So if someone tries to show somebody elses tickets they will see their own instead.
Merge pull request #174 from azul/bugfix/admin-navigates-all-tickets

Admin navigates all tickets - fixes #5879
Added allow_registration toggle.

- default is true
- See issue #5217
- See companion change in leap_platform.
Merge pull request #178 from fbernitt/issue_5217_allow_registration

Added allow_registration toggle.
store expiry with cert fingerprints

We used to store the creation date but this way it's easier to query for non expired certs
Identity view cert_fingerprints_by_expiry

Also move complex identity views into js designs.
Includes test.

Here's how you would query it from outside rails:
```
$ curl
'localhost:5984/identities/_design/Identity/_view/cert_fingerprints_by_expiry?startkey="2014-07-05"'
{"total_rows":4,"offset":1,"rows":[
{"id":"6c9091d4f13eaeaa6062c9d0528fd34d","key":"2014-07-05","value":"fingerprint"},
{"id":"6f3aa93828b4f6978d551f2623b9d103","key":"2014-07-05","value":"fingerprint"},
{"id":"b6cafacfa65042679691cd5065fb19e3","key":"2014-07-07","value":"fp"}
]}
```

Note that the expiry will be used as the key. So you should use the
current data (or yesterday) as the startkey to get all fingerprints that
have not expired yet.

The fingerprint itself is in the value. No need to include docs.
fix tests and simplify time calculations
minor: fix typo in load_views

It removed most of the reduce functions... really not what we wanted