Fix goroutine leaks

[Wentao0312]

Summary

This PR addresses potential goroutine leaks in the DTE library, specifically in:

• ConfigurationHandler.go
• ModelResult.go

In certain execution paths, goroutines may be started but are not guaranteed to exit, which can lead to leaks over time in long-running services.

Problem

During integration and testing, we observed behavior consistent with goroutine leaks originating from these components. Over time, this can:

• increase memory usage
• leave background goroutines running indefinitely
• impact system stability under sustained load

Expected behavior

All goroutines spawned by the library should terminate cleanly when:

• the associated work is completed
• a timeout or cancellation occurs
• the caller no longer needs the result

Actual behavior

Some goroutines may remain blocked or alive longer than expected, resulting in resource leakage.

Changes

• Ensure goroutines have proper termination conditions
• Add/propagate cancellation handling where needed
• Prevent goroutines from blocking indefinitely

Notes

This issue was identified during integration in a production-like environment. The changes aim to make goroutine lifecycle management more robust without altering existing functionality.

Happy to iterate further if there are preferred patterns for concurrency management in this project.