prepend 'impactstory-' to several classes in embed.

This will keep them getting confused with other classes on the host
page. Not a perfect solution as there are a few other classes we apply
that could get confused, too, but much less likely than the ones
pointed out by Alf at PeerJ. Longer term fix, I think, is maybe getting
rid of boolean widget data- attributes, and making them all strings
for consistancy. This should work fine for now, though.
try easy way to test https
removed debugging code in ti-aliaslist.js causing Go button to fail.
add https support for impactstory.js
disable mixpanel in impactstory.js
remove mixpanel script from impactstory.js libs.
add 404 error message for item in impactstory.js
remove YUI compression from impactstory.js libs.
add cache:false to ajax get in item.

IE may be caching calls, and that's why it's not working.