Remove applyPageScaleFactorinCompositor in settings.in

Source/core/frame/Settings.in

 # Defines properties which are available on the Settings object.
 #
 # Please think carefully before adding a new Setting.  Some questions to
 # consider are:
 # - Should this be a RuntimeEnabledFeature instead? Settings are for things
 #   which we support either values of at runtime.  Features are set at renderer
 #   process startup and are never changed. Features also tend to be set to a
 #   value based on the platform or the stability of the code in question, where
 #   as settings both codepaths need to be stable.
 # - How will you ensure test coverage of all relevant values of your setting?
@@ skipping 163 matching lines @@
 
 fixedPositionCreatesStackingContext initial=false
 syncXHRInDocumentsEnabled initial=true
 cookieEnabled initial=true
 mediaEnabled initial=true
 DOMPasteAllowed initial=false
 
 threadedHTMLParser initial=false
 useThreadedHTMLParserForDataURLs initial=false
 
-applyPageScaleFactorInCompositor initial=false
-
 allowCustomScrollbarInMainFrame initial=true
 webSecurityEnabled initial=true
 
 # Special keyboard navigation mode intented for platforms with no
 # proper mouse or touch support, such as a TV controller with a remote.
 spatialNavigationEnabled initial=false
 
 # This setting adds a means to enable/disable touch initiated drag & drop. If
 # enabled, the user can initiate drag using long press.
 # crbug.com/304894 tracks removal once it's been enabled on all platforms.
@@ skipping 84 matching lines @@
 touchEventEmulationEnabled initial=false
 
 
 # FIXME: This is a temporary flag and should be removed once
 # accelerated overflow scroll is ready (crbug.com/254111).
 compositorDrivenAcceleratedScrollingEnabled initial=false
 
 # FIXME: This is a temporary flag and should be removed
 # when squashing is ready. (crbug.com/261605)
 layerSquashingEnabled initial=false