Geo - Fix wikis/designs with no repository on the primary trying to sync over and over

What does this MR do?

In some cases, the repository does not exist on the primary node, but the only way to know about this is to parse the error text on the Geo secondary node. If it does not exist, we should consider it as successfully downloaded. But a change introduced in GitLab %13.3 to add support for group wikis changed the error message, see !34673 (diffs). So instead of marking the repository as synced, we try o resync it over and over.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related issue

#258658 (closed)