added workflow for autocommenting on closing an issue

[Asymtode712]

Pull Request for DL-Simplified 💡

Issue Title : #624

• Info about the related issue (Aim of the project) : This feature aims to solve the problem of poor communication and lack of acknowledgment when issues are closed. By automatically commenting on closed issues, it ensures that contributors are informed about the closure and are thanked for their efforts. This helps maintain a positive and engaging community atmosphere, encouraging continued contributions and fostering good relationships between maintainers and contributors.
• Name: Siddheya Kulkarni
• GitHub ID: https://github.com/Asymtode712
• Email ID: siddheyakul@gmail.com
• Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a JWOC 2022 participant it's, JWOC Participant) GSSOC'24

Closes: #624

Type of change ☑️

What sort of change have you made:

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Code style update (formatting, local variables)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

Checklist: ☑️

• [X] My code follows the guidelines of this project.
• [X] I have performed a self-review of my own code.
• [ ] I have commented my code, particularly wherever it was hard to understand.
• [ ] I have made corresponding changes to the documentation.
• [X] My changes generate no new warnings.
• [X] I have added things that prove my fix is effective or that my feature works.
• [X] Any dependent changes have been merged and published in downstream modules.

[github-actions[bot]]

Our team will soon review your PR. Thanks @Asymtode712 :)

[Asymtode712]

@abhisheks008 please review and merge this PR

[Asymtode712]

@abhisheks008 I have done the changes as requested by you, now the comment would only be added if the issue is closed due to merging of a linked PR and wouldn't appear if it is a spam issue and is manually closed by a maintainer.

Please review and merge this PR