Follow up: Compare write-ahead replication log for `sidekiq server replica`

What does this MR do?

In case that we didn't perform any writes before scheduling the job, it is possible to happen that the current replica has a different write-ahead replication log location from the sidekiq server replica.

If this is the case, we will read the current replica's last write-ahead replication log on the client-side, when we schedule the job, if the write was not performed.

On the Sidekiq server, we are checking if the current replica is up to date.

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because this is not a user facing change.
• 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 to #328697 (closed)