Move full timing info setting outside of processResponseEndOfBody steps

The full timing info is there for navigation timing, which is already available at document creation (which happens right after the handover).

Implementations have and WPT tests the correct behavior already.

Author: noamr

fetch.bs

@@ -4851,17 +4851,17 @@ steps:
   <p>The user agent may decide to expose `<code>Server-Timing</code>` headers to non-secure contexts
   requests as well.
 
+ <li><p>If <var>fetchParams</var>'s <a for="fetch params">request</a>'s
+ <a for=request>destination</a> is "<code>document</code>", then set <var>fetchParams</var>'s
+ <a for="fetch params">controller</a>'s <a for="fetch controller">full timing info</a> to
+ <var>fetchParams</var>'s <a for="fetch params">timing info</a>.
+
  <li>
   <p>Let <var>processResponseEndOfBody</var> be the following steps:
 
   <ol>
    <li><p>Let <var>unsafeEndTime</var> be the <a>unsafe shared current time</a>.
 
-   <li><p>If <var>fetchParams</var>'s <a for="fetch params">request</a>'s
-   <a for=request>destination</a> is "<code>document</code>", then set <var>fetchParams</var>'s
-   <a for="fetch params">controller</a>'s <a for="fetch controller">full timing info</a> to
-   <var>fetchParams</var>'s <a for="fetch params">timing info</a>.
-
    <li>
     <p>Set <var>fetchParams</var>'s <a for="fetch params">controller</a>'s
     <a for="fetch controller">report timing steps</a> to the following steps given a