WIP no recreate and log compose changes

[Marketen]

This pull request makes improvements to how Docker Compose files are managed and containers are recreated, focusing on preventing unnecessary container restarts and ensuring accurate detection of configuration changes. The main changes involve removing hardcoded DNS entries, updating test cases, and enhancing the logic for detecting and handling compose file modifications in the StakerComponent.

Compose file management improvements:

• Updated ComposeEditor to use delete service.dns instead of setting it to undefined, preventing dns: null from appearing in the YAML and avoiding unnecessary container recreation by Docker Compose.

Test updates for DNS removal:

• Modified unit tests in network.test.ts to remove references to dns: undefined, aligning tests with the updated compose file logic. [1] [2]

StakerComponent enhancements:

• Added logic in StakerComponent to read the compose YAML before and after applying user settings, detect actual changes, and only allow Docker Compose to recreate containers when the file has changed—otherwise, it uses --no-recreate to minimize downtime.
• Introduced fs import to support reading compose files for change detection.

[github-actions]

🚀 Deployed on https://69aeb4cf820617ffa16e883d--objective-borg-9eeae5.netlify.app