[DarkMode] remove enableLegacyPatching option

The option was only allowed to be set to `false`, so it's not been
used at all, so now we can remove it, given that we've had the dark
mode legacy patching disabled without any major bugs in the past few
weeks.

Bug: chromium:1152736
Change-Id: I1e794d75f9c354a0d16b1b3975f7ebdf82b3448b
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2988303
Commit-Queue: Jack Franklin <[email protected]>
Reviewed-by: Paul Lewis <[email protected]>
diff --git a/front_end/panels/application/BackgroundServiceView.ts b/front_end/panels/application/BackgroundServiceView.ts
index 45ccd0a..e36ec4d 100644
--- a/front_end/panels/application/BackgroundServiceView.ts
+++ b/front_end/panels/application/BackgroundServiceView.ts
@@ -157,8 +157,8 @@
 
   constructor(serviceName: Protocol.BackgroundService.ServiceName, model: BackgroundServiceModel) {
     super(true);
-    this.registerRequiredCSS('panels/application/backgroundServiceView.css', {enableLegacyPatching: false});
-    this.registerRequiredCSS('ui/legacy/emptyWidget.css', {enableLegacyPatching: false});
+    this.registerRequiredCSS('panels/application/backgroundServiceView.css');
+    this.registerRequiredCSS('ui/legacy/emptyWidget.css');
 
     this._serviceName = serviceName;