#10154 refactor: Remove dev-only setting resolution debug logs Pull request opened by edgarrmondragon Description These were gated by

SettingService.LOGGING

, which the end user had no control of, so they were really only there to help maintainers debug settings resolution. There are arguably better ways to debug, so removing them makes sense. Checklist • I have read the contribution guide Was generative AI tooling used to co-author this PR? • Yes (please specify the tool below) Related Issues • Closes #XXXX Summary by Sourcery Simplify settings management by removing development-only debug logging from settings stores and service. Enhancements: • Remove the settings service logging flag, logger usage, and helper methods tied to debug logging. • Clean up debug log statements related to reading, setting, and unsetting configuration values across environment, dotenv, YAML, and database stores. Summary by Sourcery Remove development-only debug logging from settings management to simplify configuration handling and avoid unused logging paths. Enhancements: • Delete the settings service logging flag, logger, and helper methods used exclusively for internal debug logging. • Remove debug log statements from environment, dotenv, YAML, and database settings stores to streamline settings operations. meltano/meltano