Fill TELESCOPE_REPORT_MAIL_TO in .env.development

[DenTray]

Description
What needs to be done?
After Telescope config publication, add writing of the TELESCOPE_REPORT_MAIL_TO variable to .env.development .
Requirements:

• Use the team lead email: $this->codeOwnerEmail (InitCommand class).
• Add TELESCOPE_REPORT_MAIL_TO only to .env.development :
• Do not add this variable to .env .
• Do not add this variable to .env.example .
  Expected Outcome
  What is the expected result?
  After running php artisan init , the generated .env.development file contains TELESCOPE_REPORT_MAIL_TO filled with the entered team lead email.

Expected result:

• .env.development contains the correct email value.
• .env does not contain this variable.
• .env.example does not contain this variable.
  Verification Scenarios
  How can this be tested?

1. Run php artisan init <application_name> and provide a value for the team lead email.
   • Confirm .env.development contains:
     • TELESCOPE_REPORT_MAIL_TO=
2. Check .env .
   • Confirm TELESCOPE_REPORT_MAIL_TO is absent.
3. Check .env.example .
   • Confirm TELESCOPE_REPORT_MAIL_TO is absent.
4. Run the related automated test.
   • Confirm the fixture in tests/fixtures/InitCommandTest/ matches the expected .env.development output.
   • Confirm the test verifies presence only in .env.development .