[Topics] Measure a misuse pattern: topics called on a page after redirects

What: When Topics API is first invoked in a page, record 1) the
number of automated client-side redirect occurred before this page,
and 2) among those redirects, the number of pages that invoked
Topics API.

Why: Topics API can be misused when a site gets topics and passes
it to the next site in the URL param via automated redirect, and
repeating this process several times allows the cooperating sites
to get all the user's topics upon a single page visit (i.e. 3 topics
per site, and 15 topics from 5 sites). Thus, we want to better
understand the usage patterns.

How: Add a WebContentsObserver that tracks the topics usage in a
chain of automated redirects, by getting the previous page's redirect
status, updating it, and initializing the next page with the updated
status. When Topics API is first used in a page, record UMA metrics.
See the class comment for `BrowsingTopicsRedirectObserver` for
details.

Bug: 329312215
Change-Id: Ie9c63a72427ed45c3eb30927b7797af200c19437
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5366010
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Reviewed-by: Robert Ogden <robertogden@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1276188}