Once bug 1665383 is fixed, the production codepath will be using the resources codepath, with resource-available/resource-updated.
And we will no longer use the networkEventUpdate / network-event-update events:
https://searchfox.org/mozilla-central/search?q=networkEventUpdate&path=&case=true&regexp=false
https://searchfox.org/mozilla-central/search?q=network-event-update&path=&case=true&regexp=false

Tests which are still using these events should be refactored to listen to NETWORK_EVENT.
These tests should be probably be removed in favor of ResourceWatcher tests:
https://searchfox.org/mozilla-central/source/devtools/shared/resources/tests
Note that some may be redundant with the existing tests.

Only legacy listeners should be using these events. And we will have to keep them in specs until we remove the legacy listeners.

Adding into the M3 reserve list, so it isn't forgotten when we are planning a follow up Clean-up sprint.

Tracking dt-fission-m3-reserve bugs for Fission M8 (blocking Release channel experiment, but not Beta experiment).

Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.