Replace loadWithOverviewMode settings with calls to shrinksViewportContentToFit

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 204 matching lines @@
 # crbug.com/304869 tracks removal.
 pinchVirtualViewportEnabled initial=false
 useSolidColorScrollbars initial=false
 pinchOverlayScrollbarThickness type=int, initial=0
 
 mainFrameClipsContent initial=true
 
 
 # Presumably used by LayoutTests?  Unclear.
 useWideViewport initial=true, invalidate=ViewportDescription
-loadWithOverviewMode initial=true, invalidate=ViewportDescription
 
 
 # Font scale factor for accessibility, applied as part of text autosizing.
 accessibilityFontScaleFactor type=double, initial=1.0, invalidate=TextAutosizing
 
 
 # Only set by Layout Tests.
 mediaTypeOverride type=String, initial="screen", invalidate=MediaType
 
 # loadsImagesAutomatically only suppresses the network load of
@@ skipping 30 matching lines @@
 
 # This value indicates the maximum number of bytes a document is allowed
 # to transmit in Beacons (via navigator.sendBeacon()) -- Beacons are
 # intended to be smaller payloads transmitted as a page is unloading, not
 # a general (one-way) network transmission API.
 # The spec ( https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/Beacon/Overview.html )
 # does not proscribe an upper limit, but allows for it -- the underlying
 # API will return 'false' in that case.
 maxBeaconTransmission type=int, initial=16384