GitLab

The client_tag_based_model_type_processor requires incoming data to
have client tag hash field set on each entity. Wallet data does not
have this field set, because the data comes from the Wallet server, as
opposed to from other clients. This makes the processor drop all
incoming updates on the ground (this code introduced here), which means
there's no data for the user.

This CL makes the bridge to create client_tags for Wallet items that
don't have the tag set yet.

A future, longer term solutions would be to either make the server set
the client tags, or to use a different processor for wallet data.

BUG=874001

Change-Id: Ie4331c3bd601a43c59fc35ea94d271db2db66ec8
Reviewed-on: https://chromium-review.googlesource.com/1174435
Commit-Queue: Florian Uunk <feuunk@chromium.org>
Reviewed-by: Tim Schumann <tschumann@chromium.org>
Cr-Commit-Position: refs/heads/master@{#584766}