Geo: Ignore remote stored objects when calculating counts

What does this MR do?

If objects (LFS objects or Job Artifacts) were synced (or failed) and they are moved to Object Storage on the primary. The secondary would still treat them as synced. But in fact, it should ignore them.

Why was this MR needed?

It was supposed to be included in gitlab-org/gitlab-ee!4689, but that won't make it into %10.6 😞. So this MR will ensure at least the counts will be correct. The actual cleanup of the objects on disk will be done by that MR.

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Review
  • Has been reviewed by UX
  • Has been reviewed by Frontend
  • Has been reviewed by Backend
  • Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered
• If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
• End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes gitlab-org/gitlab-ee#4971

gitlab-org/gitlab-ee#4215