GitLab

Move cloud token data out of WalletMaskedCreditCard and make it a
separate sync data type.

Reason is: In the future, one actual card can have multiple sets of
cloud token data so we need to change this field to a repeated one,
but converting a sync data type with repeated field to data that
can be stored in the autofill table is pretty complex. There is no reason
to do that since the cloud token data will be stored in a separate table
anyway. As long as there is a server id that can be used to match the
actual card and the cloud token data of the card, we should be fine.

Bug: 1020740
Change-Id: I1595d3dccf2b154b3fcaea59e710b75d07a692ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1897004
Commit-Queue: Siyu An <siyua@chromium.org>
Reviewed-by: Jared Saul <jsaul@google.com>
Reviewed-by: Christos Froussios <cfroussios@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#714075}