[fix][broker] Avoid misleading ownership lock expiry logs during shutdown - #26633

Motivation

When broker deregistration fails during shutdown, graceful bundle unloading is skipped and the coordination service releases the remaining ownership locks directly. These locks are still registered in OwnershipCache, so their release callbacks incorrectly report them as expired at INFO level.

This follow-up to #26533 avoids misleading expiry messages during shutdown.

Modifications

• Log ownership lock expiry at INFO only while the broker is running, and at DEBUG during shutdown.
• Preserve lock registration removal and ownership cleanup.
• Add regression tests using a real ZooKeeper server and broker to cover shutdown with failed deregistration and actual lock expiry while running.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment