Add automation to unassign author from stale issues

[nihal467]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[thedevildude]

@nihal467 I found this workflow which can be used with our existing stale workflow to solve this issue. Do take a look at it. https://github.com/BoundfoxStudios/action-unassign-contributor-after-days-of-inactivity

Other approach I could think of was writing manual CLI commands to unassign issues.

[rithviknishad]

@thedevildude we already have the stale bot right? It supports output of the list of issues/prs marked as stale / closed due to inactivity (ref: https://github.com/actions/stale?tab=readme-ov-file#list-of-output-options).

Maybe we could use this output and do the necessary unassign based on the output from this itself?

[thedevildude]

@rithviknishad We can store the output from the stale bot and then use github-scripts actions to run a script that loops on the output and calls github.issues.removeAssignees()?

[rithviknishad]

yeah

[rithviknishad]

Add a comment too tagging the assignees why there were unassigned too.

[thedevildude]

@rithviknishad Got it, I'd like to work on if it's unblocked

[nihal467]

existing workflow looks good, upon re-evaluating, will be creating a new issue for better management, if required