v5.9.7: Enable console commands to opt out of file-system locking

The default file-system lock, when shared across multiple application hosts, caused issues for commands like `ConsumersControlCommand`. These commands need to run independently on each host to publish control messages to all consumer instances. The shared lock prevented this, leading to inconsistent behavior where some consumers might not receive updates.

This change introduces an `isLockRequired()` method, allowing specific commands to bypass the locking mechanism and operate correctly in distributed environments.