Add workflow for closing stale issues and PRs

[ChenYi015]

Purpose of this PR

Add workflow for closing staled issues and PRs:

• The issues/PRs will be marked as stale for 60 days with no activity and will be closed after 30 days with no activity.

Change Category

Indicate the type of change by marking the applicable boxes:

• Bugfix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that could affect existing functionality)
• Documentation update

Rationale

Checklist

Before submitting your PR, please review the following:

• I have conducted a self-review of my own code.
• I have updated documentation accordingly.
• I have added tests that prove my changes are effective or that my feature works.
• Existing unit tests pass locally with my changes.

Additional Notes

[ChenYi015]

/assign @vara-bonthu

[vara-bonthu]

Thanks for adding this. I believe it's essential for maintaining the repo and encourages contributors to reopen PRs and issues if they still think they are necessary. Given the many open PRs and issues, this could close most of them.

I want to ensure all maintainers and reviewers are okay with this approach.
@yuchaoran2011 @andreyvelich

[yuchaoran2011]

This will be a good topic for the community meeting next week. Let's gather more input before making a decision

[yuchaoran2011]

As discussed during the most recent community call, attendees have agreed on giving this new process of managing issues and PRs a try
/lgtm

[yuchaoran2011]

/lgtm

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vara-bonthu, yuchaoran2011

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vara-bonthu,yuchaoran2011]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment