Renaming kpi_backend_db_hostname and port to kpi_backend_db_url. Updated with KPIggybank endpoint, posting form data

* If the controller's "continuation" option is specified, start saving data immediately to localStorage.
* in start.js, look for CREATE_EMAIL and ADD_EMAIL on the window.location.hash. If this exists, the dialog session is a continuation.
* Add some more tests.

Other notable changes:
* Send old interaction data irregardless of whether the current dialog session is collecting data.
* Because of this above change, simplified storage regarding data.
* Make sure when sampling is enabled, data is saved.
* Make sure when sampling is disabled, data is not saved.
* Added tests to test expected flow.

modify interaction_data api to always return a quick success, update hub.js to add an .all() function that subscribes to all published events, interaction_data module now adds all published events to event stream

implement frontend interaction_data mechanisms, still require tests, event_stream population, and reduced UA information parsing

Change the order of assertion generation to be after the user is asked "is this your computer?"

Update remaining reset_password test to deal with new flow when the user confirms the address.

* This fixes a problem where it is possible that a user takes more than 2 minutes to answer, making the already generated assertion invalid.
* A lot of general cleanup of the state machine.
* Push all post email selection flows to a new state, "email_valid_and_ready" which decides whether to ask the user the computer ownership status.
* Assertions are generated after the "is this your computer" is asked.
* doEmailChosen is replaced with doGenerateAssertion - there were multiple calls to generate an assertion, not very DRY.
* Fix a problem in network.js where a user who completes user registration should be marked as authenticated.
* rename email_chosen.js to generate_assertion.js to clarify its purpose.

issue #1460

Fix reset password completion not generating an assertion.

issue #1508

IE6 and IE7 fixes for the unsupported dialog.

Fix IE6 and IE7 throwing exceptions in the communication iframe.

issue #1496

* include.js - check to ensure the browser is supported before setting up the communication_iframe.  Adding the iframe in unsupported browsers will cause an exception within the iframe.

issue #1390

Conflicts:

	resources/static/include_js/include.js
	resources/static/shared/storage.js

Add a cookie check to most main site pages.

* The catch all will print a console log message if console.log is available.
* Adding helpers.log which prints to the console if console.log is available.