[sync] Rename term 'secondary' with 'explicit' wrt passphrase

No behavioral changes, it's a fully automated replacement of the term.

The new name is consistent with other code like
syncer::IsExplicitPassphrase(). This logic returns true mainly for
custom passphrase users but also for the legacy
frozen-implicit-passphrase users (very similar to custom passphrase).

Change-Id: Id7ccbfaeef8fa995ca669e6040ef276bd18c0d3b
Bug: 1016715
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2821541
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Reviewed-by: Thomas Tangl <tangltom@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#875102}
GitOrigin-RevId: 930e2af1d16616915d2190503be1ccee143e1b53
6 files changed