smp should go both ways

fixes for #465

including,

* adds a case for smp aborting
* adds an argument to the smp callback with the users action `(answered|asked)`
* checks that a secret is provided ( `answer.length > 0`) before submitting
* check for `chrome.storage`, only available in the chome app (ie. breaks standalone testing in chrome with `npm start`)
* add jquery sourcemap file
* change secret field to password, for obfuscation
* authentication should be paired with long-lived keys. currently the cc implementation is vulnerable to an active adversary who waits for authentication to have taken place and then forces otr to rekey, which happens opaquely to the user. a line is added to reset the trust state on ake success but that probably is not enough. a notification that the trust state has changed would be good. similarly, a suggestion to authenticate at the beginning of each private chat might be merited.