fix triggerer logger's file descriptor closed when it removed

[wjddn279]

closed: #61916

An issue was reported where file descriptors were not being properly closed when the logger was destroyed in the existing triggerer.

As shown below, the number of open file descriptors was continuously increasing before this fix. After applying the logic in this PR, file descriptors are now properly closed and the count decreases as expected.

Additionally, we confirmed through added logging that the logger is properly garbage collected after upload_to_remote is called, triggering the destructor as expected.

AS-IS (3.1.7)

TO-BE (patched)

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[eladkal]

Can you add a test to avoid regression?

[wjddn279]

sure. I'll add it

[wjddn279]

@eladkal Done!