[common]: Add logging to setEnableWrites to track PUSHED to ONLINE version transitions

[misyel]

Problem Statement

When investigating deferred version swap issues, it's difficult to determine when and why a version's status changed from PUSHED to ONLINE in non-target regions. The setEnableWrites(true) method in ZKStore has a side effect that calls setPushedVersionsOnline(), which converts ALL PUSHED versions to ONLINE status. Without logging, it's impossible to trace when this occurs.

Solution

Added INFO level logging to ZKStore.java:

• Log when setEnableWrites(true) is called, including the store name
• Log each version that gets changed from PUSHED to ONLINE in setPushedVersionsOnline(), including version number and store name

New log messages:

setEnableWrites(true) called for store {storeName}. Will check for PUSHED versions to mark ONLINE.
setPushedVersionsOnline: Changing version {versionNumber} of store {storeName} from {status} to ONLINE.

Code changes

• Added new code behind a config.
• Introduced new log lines.

Concurrency-Specific Checks

• Code has no race conditions or thread safety issues.
• Proper synchronization mechanisms are used where needed.
• No blocking calls inside critical sections.
• Verified thread-safe collections are used.
• Validated proper exception handling in multi-threaded code.

How was this PR tested?

• New unit tests added.
• New integration tests added.
• Modified or extended existing tests.
• Verified backward compatibility (if applicable).

Existing tests pass. This is a logging-only change with no behavioral modifications.

Does this PR introduce any user-facing or breaking changes?

• No. You can skip the rest of this section.