tst_SecurityStatus fails in single process

[Chris Coulson]

FAIL! : qml-api-single-process-test::SecurityStatus::test_SecurityStatus1(row 7) Compared values are not the same
   Actual (): 4
   Expected (): 3
   Loc: [/home/chr1s/src/oxide/unit-testing/qt/tests/qmltests/api/tst_SecurityStatus.qml(200)]
QWARN : qml-api-single-process-test::SecurityStatus::test_SecurityStatus1(row 8) OxideQQuickWebView: context is read-only in single process mode. The webview will automatically use the application-wide default WebContext
[0402/164814:ERROR:layer_tree_host_impl.cc(2205)] Forcing zero-copy tile initialization as worker context is missing
127.0.0.1 - - [02/Apr/2016 16:48:14] "GET /tst_SecurityStatus_run_insecure_content_in_iframe.html HTTP/1.1" 200 -
[0402/164814:WARNING:web_contents_impl.cc(3269)] https://testsuite/ ran insecure content from http://testsuite/tst_SecurityStatus_script.js
[0402/164814:WARNING:web_contents_impl.cc(3269)] https://testsuite/ ran insecure content from http://testsuite/tst_SecurityStatus_script.js
FAIL! : qml-api-single-process-test::SecurityStatus::test_SecurityStatus1(row 8) Compared values are not the same
   Actual (): 1
   Expected (): 2
   Loc: [/home/chr1s/src/oxide/unit-testing/qt/tests/qmltests/api/tst_SecurityStatus.qml(208)]

The issue here is that running insecure scripts taints host/process combinations for the rest of the session, and each test assumes that they get their own process. Because that's not the case with single-process, earlier tests taint subsequent tests, causing them to fail