[TDR] Remove TODOs linked to issue 40186079

This CL was generated by an AI agent and verified by the CL owner before
sending for review. The TODOs were identified as stale by TODO Removal
Agent (http://go/dead-todo-removal-agent).
* Detailed reasoning can be found in the CL comments.
* How to review this CL: http://go/tdr-review-instructions
* To opt-out from future reviews: http://go/tdr-opt-out.

The TODO suggests a refactoring that was tracked by a bug now marked as
'OBSOLETE'. The bug was closed because the proposed change was deemed
"not directly actionable," making the TODO's goal irrelevant.

Change-Id: Idde6aaab23a022816850cb9548f09797435e7cdc
Bug: 40186079
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/7241814
Reviewed-by: Danil Somsikov <[email protected]>
Reviewed-by: Benedikt Meurer <[email protected]>
Commit-Queue: Kuba Mikulski <[email protected]>

Author: Kuba Mikulski

front_end/core/sdk/NetworkManager.ts

@@ -2716,13 +2716,6 @@ export interface Conditions {
   packetLoss?: number;
   packetQueueLength?: number;
   packetReordering?: boolean;
-  // TODO(crbug.com/1219425): In the future, it might be worthwhile to
-  // consider avoiding mixing up presentation state (e.g.: displayed
-  // titles) with behavioral state (e.g.: the throttling amounts). In
-  // this particular case, the title (along with other properties)
-  // doubles as both part of group of fields which (loosely) uniquely
-  // identify instances, as well as the literal string displayed in the
-  // UI, which leads to complications around persistance.
   // TODO(crbug.com/422682525): make this just a function because we use lazy string everywhere.
   title: string|(() => string);
   // Instances may be serialized to local storage, so localized titles