Refactor: guard all logger calls with isXxxEnabled() checks

[Copilot]

Unguarded logger calls evaluate their arguments eagerly regardless of log level, causing unnecessary string construction, method calls, and lambda execution at runtime.

Changes

• Wrapped all logger.trace(...), logger.info(...), and logger.warn(...) calls across 7 files in the appropriate isXxxEnabled() guard
• Grouped consecutive trace calls (e.g. forEach lambda in ServiceInstanceUtils) under a single guard block to avoid redundant level checks

Before:

logger.trace("The ServerProperties property is changed to: {}", getProperties(environment, serverPropertyNames));

After:

if (logger.isTraceEnabled()) {
    logger.trace("The ServerProperties property is changed to: {}", getProperties(environment, serverPropertyNames));
}

Files affected

File	Level	Calls
DecoratedFeignComponent	trace	2
FeignClientSpecificationPostProcessor	trace	1
TomcatDynamicConfigurationListener	trace	3
ServiceInstanceUtils	trace	3 (incl. forEach lambda)
ServiceRegistrationEndpoint	info, warn	2
ServiceDeregistrationEndpoint	info, warn	2
WebServiceRegistryAutoConfiguration	trace	1

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud