Fix module injection to continue processing remaining properties

[LucHeart]

Summary

• ensure module component activation skips already-set properties without aborting the rest of the injections

Testing

• not run (dotnet SDK not available in container)

---

https://chatgpt.com/codex/tasks/task_e_68fa1fd236448327bbcc61ed18e99b58

[Copilot]

Pull Request Overview

This PR fixes a bug in the module dependency injection logic where encountering a property that's already been set would cause the injection process to abort prematurely, preventing subsequent properties from being injected.

Key Changes:

• Changed early return to continue statement in property injection loop to ensure all properties are processed

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The change from return to continue correctly fixes the logic to process all properties in the injection loop. However, verify that the loop iterating over properties properly handles any exceptions that might be thrown during individual property injections, to ensure one failing property doesn't prevent others from being injected.