fix(server):fix graph server cache notifier mechanism

[haohao0103]

fix #2728

[Copilot]

Pull Request Overview

This PR fixes the graph server cache notifier mechanism by introducing a controlled registration of cache listeners via static maps and enhancing logging during cache event processing.

• Introduces static ConcurrentHashMaps (graphCacheListenStatus and storeEventListenStatus) for managing listener registration.
• Updates listener registration and unregistration in CachedGraphTransaction using the new maps.
• Enhances logging in the AbstractCacheNotifier in StandardHugeGraph for better traceability.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
hugegraph-core/src/main/java/org/apache/hugegraph/backend/tx/GraphTransaction.java	Added static maps for tracking cache listener registration.
hugegraph-core/src/main/java/org/apache/hugegraph/backend/cache/CachedGraphTransaction.java	Updated cache and store event listener registration/unregistration using static maps.
hugegraph-core/src/main/java/org/apache/hugegraph/StandardHugeGraph.java	Enhanced logging within the cache notifier for improved debugging.

Comments suppressed due to low confidence (1)

hugegraph-server/hugegraph-core/src/main/java/org/apache/hugegraph/backend/cache/CachedGraphTransaction.java:194

• Using static ConcurrentHashMaps to track listener registration may cause unintended unregistrations if multiple CachedGraphTransaction instances share the same graph name. Consider implementing a reference counting mechanism or a more granular registry to ensure that an active listener is not removed prematurely.

String graphName = this.params().name();