Profile processing only works properly in Firefox

`new URL("moz-extension://08fb0bab-91a5-43dd-8872-fddac8b38dea/").origin` is `null` in non-Firefox browsers.

If you use `await Services.profiler.dumpProfileToFileAsync(...)` in Firefox, and then load the file into profiler.firefox.com running in Chrome, then profile processing creates an incorrect `resourceTable`, mapping all add-on functions to the first extension.

Example: https://share.firefox.dev/4fj4bT0 (shows "Okta Browser Plugin", should be showing "1Password – Password Manager")

┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FP-921)

Trace the profile-processing path that builds the resourceTable, focusing on handling of moz-extension URLs and URL.origin. Reproduce the issue by loading a Firefox-dumped profile into profiler.firefox.com in Chrome and compare the extension attribution with the linked example. Done means add-on functions are mapped to the correct extension outside Firefox.

Written by the indexing model from the issue text.