wrap the schema load into one transaction so it's easier for me to catch my innumerable mistakes
mistake #1: still referencing the icon_id (which has been removed for now so i can focus just on what i plan to implement in the short term)
set template path manually so that failed registration submits' ->forwards don't error out anymore
carry over previous inputs on error
tell Captcha::reCAPTCHA to use SSL, since we force that everywhere
typo fix in redirection to account verification page (account not accout)
perform basic remote API key verification - just enough to get the key type and access mask
convert blanket not-null on eve.api_keys.key_type to a constraint allowing null when the key has not yet been verified (since we don't know the key type until we contact the remote API)
relocate the errors/field_errors stash keys initialization into the Root controller's auto method, since they'll be used widely throughout the application
pull in account's keys for listing on the API Keys page
need to enforce lc() on key type to meet constraint (and to simplify values incoming from CCP API for our internal use)
fix redirect after adding valid API key to account (drop the /index part of the uri_for argument)
display more details of keys on account for API index
set newly-added and verified keys to active, not just verified -- otherwise the forthcoming API querying jobs will ignore them
add links to api key list for activation/deactivation/verification -- depending on key's current state