Enable offline support for all DevTools screens

Enabling offline support will:

1. Be helpful for users who want to export data and reload later or to send to other developers for debugging
2. Be _especially_ helpful for faking test data while developing DevTools. Then we can just write `SomeScreenData.parse(someOfflineData)` to initialize fake testing data for the screen. If we continue to integrate with Stager, this will be useful for both testing and stager development (see [https://github.com/flutter/devtools/pull/446](https://github.com/flutter/devtools/pull/4463))
3. Be helpful for users to be able to include in bug reports

- [ ] Inspector - https://github.com/flutter/devtools/issues/1966
- [x] Performance - done
- [x] CPU Profiler - already done, but need to ensure we are including any filters that are set on the data
- [x] Memory Profiler - need to switch to how other screens export data and send data to Downloads (https://github.com/flutter/devtools/issues/3411) and need to audit to ensure that all data from screen is included in the output - https://github.com/flutter/devtools/issues/6759
- [ ] Debugger - is there a use case for looking at an "offline" debugger state? This is still useful for creating test data files, but we may want to make these methods visibleForTesting and potentially only expose for debug builds of the DevTools app if we don't want to expose an "Export" button for users.
- [x] Network - we have an "Export as Har" function, but we need to hook this up to our existing import / export framework and ensure that all data to recreate the state of the screen for offline uses is included in the output (e.g. selected request, filters, etc.)
- https://github.com/flutter/devtools/pull/8332
- https://github.com/flutter/devtools/pull/8886
- [ ] Logging (https://github.com/flutter/devtools/issues/29)
- [ ] App Size (https://github.com/flutter/devtools/issues/8110)
- [ ] Vm Developer Tools Screen

Inizia esaminando gli elementi dello schermo non selezionati e le issue collegate, in particolare Inspector (#1966), Logging (#29) e App Size (#8110), quindi confronta le schermate completate e le pull request di Network (#8332 e #8886). Il lavoro è considerato completato quando ogni schermata DevTools applicabile può esportare e ricaricare lo stato completo, inclusi filtri e selezioni, e i casi d’uso con dati di test sono stati gestiti o esplicitamente esclusi.

Scritto dal modello di indicizzazione a partire dal testo della issue.