After registered/activated an in-scope SW, we create a new Worker(in-scope-url) from a *controlled* page, although this Worker can get controlled by the SW, we found it has exactly the same client id with the page starting it.

This is because the Worker is reusing ServiceWorkerNetworkProvider of the page which started it, meaning that all fetch requests originating from the Worker will be intercepted just like they're coming from that page. 

Instead of reusing, we need to let DedicatedWorker have its own ServiceWorkerNetworkProvider, just like other SW clients(page, shared worker).

wpt test:
external/wpt/service-workers/service-worker/clients-get-client-types.https.html