Allow downgrade versions earlier than the bundled version

Component Update supports downgrading of versions in order to support
rollbacks. However, if the component is also bundled, then currently
you can not rollback to a version earlier than the bundled version.
Adding support so that the bundled version is skipped if it has been
seen before and there is a downgrade.

This is done by keeping track of the maximum previous version in the
component updater preferences for the component (as `max_pv`).
In the case of a downgrade (say v2 reverted back to v1), then v2 would
be saved as the previous max, and when selecting which version to use,
the bundled version will only be used if its version is greater than
this saved max. If the bundled version changes to something bigger
(say v3), then it will be used instead of v1.

Bug: 1445973
Test: Manual check plus new unit tests pass
Change-Id: Id533a80e9e83a142b12941cdae37957430042e22
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5238641
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: John Rummell <jrummell@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1253986}

• chrome/updater/persisted_data.cc[diff]
• chrome/updater/persisted_data.h[diff]
• components/component_updater/component_installer.cc[diff]
• components/component_updater/component_installer.h[diff]
• components/component_updater/component_installer_unittest.cc[diff]
• components/component_updater/component_updater_service.cc[diff]
• components/component_updater/component_updater_service.h[diff]
• components/component_updater/component_updater_service_internal.h[diff]
• components/component_updater/mock_component_updater_service.h[diff]
• components/update_client/component.cc[diff]
• components/update_client/persisted_data.cc[diff]
• components/update_client/persisted_data.h[diff]
• components/update_client/persisted_data_unittest.cc[diff]