officejs_support_request_ui_test: check service worker first

This might fix flaky "testLogin". One theory is that a service worker
request to fill the cache happens while the selenium browser logs out,
which cause browser to keeps the authentication cookie.

This test waits for service worker to have filled the cache. We also
change the name (00) to run it first, so that subsequent tests are
executed with the cache already pre-filled.

bt5/erp5_officejs_support_request_ui_test/PathTemplateItem/portal_tests/officejs_support_request_ui_zuite/testServiceWorker.xml → bt5/erp5_officejs_support_request_ui_test/PathTemplateItem/portal_tests/officejs_support_request_ui_zuite/test00ServiceWorker.xml

@@ -46,7 +46,7 @@
         </item>
         <item>
             <key> <string>id</string> </key>
-            <value> <string>testServiceWorker</string> </value>
+            <value> <string>test00ServiceWorker</string> </value>
         </item>
         <item>
             <key> <string>output_encoding</string> </key>

bt5/erp5_officejs_support_request_ui_test/PathTemplateItem/portal_tests/officejs_support_request_ui_zuite/testServiceWorker.zpt → bt5/erp5_officejs_support_request_ui_test/PathTemplateItem/portal_tests/officejs_support_request_ui_zuite/test00ServiceWorker.zpt

@@ -11,6 +11,21 @@
 </thead><tbody>
 <tal:block metal:use-macro="here/Zuite_CommonTemplate/macros/init" />
 
+<tr>
+  <td colspan="3"><b>Check default web site service worker, also to fill cache</b></td>
+</tr>
+<tr>
+  <td>open</td>
+  <td>${base_url}/web_site_module/erp5_officejs_support_request_ui/#/?page=test_service_worker</td>
+  <td></td>
+</tr>
+<tal:block metal:use-macro="here/Zuite_CommonTemplateForRenderjsUi/macros/wait_for_app_loaded" />
+<tr>
+  <td>waitForTextPresent</td>
+  <td>Has SW: true</td>
+  <td></td>
+</tr>
+
 <tr>
   <td colspan="3"><b tal:content="python: 'Clone web site'"></b></td>
 </tr>