Move shouldGetPageLoadMetrics to notifyPageLoadMetrics.

This ensures that the shouldGetPageLoadMetrics policy is applied
consistently to all page load metrics, as some invoke
notifyPageLoadMetrics directly, bypassing the check that was
previously in notifySinglePageLoadMetric.

Change-Id: Iecc8f88ae9a5062894513d89483238a52d8c3f5a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1773888Reviewed-by: Benoit L <lizeb@chromium.org>
Commit-Queue: Bryan McQuade <bmcquade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#692308}

chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabsConnection.java

@@ -1155,7 +1155,6 @@ public class CustomTabsConnection {
      */
     boolean notifySinglePageLoadMetric(CustomTabsSessionToken session, String metricName,
             long navigationStartTick, long offsetMs) {
-        if (!mClientManager.shouldGetPageLoadMetrics(session)) return false;
         if (!mNativeTickOffsetUsComputed) {
             // Compute offset from time ticks to uptimeMillis.
             mNativeTickOffsetUsComputed = true;
@@ -1186,6 +1185,7 @@ public class CustomTabsConnection {
      *     should be a key specifying the metric name and the metric value as the value.
      */
     boolean notifyPageLoadMetrics(CustomTabsSessionToken session, Bundle args) {
+        if (!mClientManager.shouldGetPageLoadMetrics(session)) return false;
         if (safeExtraCallback(session, PAGE_LOAD_METRICS_CALLBACK, args)) {
             logPageLoadMetricsCallback(args);
             return true;