Initial take at storing settings in the db.
- Split settings into deployment settings and
  jabbr settings.
- Store settings as json string in the db.
- Generate keys for auth on initial load.
- Cache settings for a day
Goodbye gate.
Allow disabling user registration.
Enhanced username/password auth.
- Make it so that jabbr can authorize users from
  an arbitrary source.
- Reimplement default u/p auth on this new interface.
Fixed some partial login issues.
- Don't add claims twice or add partial identity twice.
Kill proxying and reuse the file upload handling instead.
- Nuke the image proxy and associated settings and just piggy back
  on file upload settings.
Only change the image url not the href
Added ISettingsManager for loading and saving settings.
Create initial administration UI
Move logic for displaying the admin button to view model instead of JS
Implement saving application changes
Use model binding on POST
Update access check and model binding to hidden field for encryption keys
Add validation when saving settings
Added generic Get<T> to CacheExtensions
Re-added the authentication provider node for now.
Made sure places that use app settings were not singletons.
Removed and sorted usings
Updated the azure build script to remove config settings that are in the db.
Don't die if we fail to load settings.
- Revert to default if the settings are malformed.