Fixes #26474 and #2688

Context

Handling the daemon logs is a long standing open issue which caused many issues over time as:

• Log files were too verbose as there was no way to change the daemon log level
• Log files never got cleaned up

This changeset introduces the following:

• A new property called org.gradle.daemon.log.level which defines the log level of the daemon. The default is set to debug (this is the current default - should we also change the default to info in this mr?)
• Code to automatically delete log files older than 2 weeks - This duration is arbitrary but better than no cleanup at all. Not sure if this should be configurable as well? I would like to keep this MR rather small to get it ready for production quicker.

Contributor Checklist

• Review Contribution Guidelines.
• Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
• Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
• Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
• Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
• Provide unit tests (under <subproject>/src/test) to verify logic.
• Update User Guide, DSL Reference, and Javadoc for public-facing changes.
• Ensure that tests pass sanity check: ./gradlew sanityCheck.
• Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet

Before merging the PR, comments starting with

• ❌ ❓must be fixed
• 🤔 💅 should be fixed
• 💭 may be fixed
• 🎉 celebrate happy things