slapos_jio_ui_test: Dont call wait for content after click proceed

   The proper way is always wait for notification message after click proceed, since the spinning icon can flick between before the post and reload the page (probably because notifySubmitted).

   This tiny flickering can cause confuse the wait_for_content macro since it is called too soon.

master/bt5/slapos_jio_ui_test/SkinTemplateItem/portal_skins/slapos_ui_test/Zuite_SlapOSCommonTemplate.zpt

@@ -687,22 +687,8 @@
         <td></td>
       </tr>
       <tr>
-        <td>waitForElementPresent</td>
-        <td>//div[contains(@data-gadget-url, 'gadget_slapos_header.html')]//button[@data-i18n="Proceed"]</td>
-        <td></td>
-      </tr>
-      <tr>
-        <td>assertElementPresent</td>
-        <td>//div[contains(@data-gadget-url, 'gadget_slapos_header.html')]//button[@data-i18n="Proceed"]</td>
-        <td></td>
-      </tr>
-      <tr>
-        <td>click</td>
-        <td>//div[contains(@data-gadget-url, 'gadget_slapos_header.html')]//button[@data-i18n="Proceed"]</td>
-        <td></td>
-      </tr>
+      <tal:block metal:use-macro="here/Zuite_SlapOSCommonTemplate/macros/click_proceed" />
     </tal:block>
-    <tal:block metal:use-macro="here/Zuite_SlapOSCommonTemplate/macros/wait_for_content_loaded" />
     <tal:block tal:define="notification_configuration python: {'class': 'success',
                                                                'text': delete_configuration['notification_text']}">
       <tal:block metal:use-macro="here/Zuite_SlapOSCommonTemplate/macros/wait_for_notification" />