Handle unexpected version number in commit response in the model type processor

ClientTagBasedModelTypeProcessor currently verifies server response
using DCHECK. Currently, we're not handling the case where the server
returns an older version than what's stored in the local metadata. This
change explicitely ignores such response from the server along with
logging.

Bug: 1351666
Change-Id: Ibbf04a8263936a5ce45cd18e5a1bf4fae15af13b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3906209
Reviewed-by: Rushan Suleymanov <rushans@google.com>
Commit-Queue: Ankush Singh <ankushkush@google.com>
Cr-Commit-Position: refs/heads/main@{#1051174}