[Subscription] Suppress expected commit progress warnings

[Caideyipi]

Description

DataNodes with subscription_enabled=false intentionally return UNSUPPORTED_OPERATION when
ConfigNode pulls commit progress. The best-effort synchronizer already ignores their progress but
then logs the expected response as a warning.

Suppress that expected status in the best-effort response loop. Other unsuccessful responses still
produce warnings, and required synchronization still rejects UNSUPPORTED_OPERATION.

Validation

• mvn spotless:apply -pl iotdb-core/confignode
• mvn -o test -pl iotdb-core/confignode -am -Dtest=CommitProgressSyncProcedureTest -Dsurefire.failIfNoSpecifiedTests=false -Ddevelocity.off=true

The focused test covers expected and unexpected responses, required synchronization, and persistence
of progress from successful DataNodes.

---

This PR has:

• been self-reviewed.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage.

---

Key changed/added classes (or packages if there are too many classes) in this PR

• CommitProgressSyncProcedure