Geo: Resync verification failures

What does this MR do?

Before

• Sync => Success
• Verify => Fail
• Retry verification later (progressive backoff)

After

• Sync => Success
• Verify => Fail
• Resync later (progressive backoff)

Resolves #301244 (closed)

Follow up

There are optimizations that we can do as a result of this change in logic. That is captured in #333461.

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)