chore(Action): add label check and auto close action

[ArgoZhang]

Link issues

fixes #5687

Summary By Copilot

This pull request introduces two new GitHub Actions workflows to manage inactive issues. These workflows automate the process of checking for inactivity and closing issues that require a response but have not received one within a specified timeframe.

New workflows added:

• .github/workflows/issue-check-inactive.yml: This workflow runs every 15 days and checks for issues labeled as 'inactive'. If an issue is labeled as 'invalid' and has not received a response in 3 days, it will be closed.
• .github/workflows/issue-close-required.yml: This workflow runs daily at 10 AM and checks for issues labeled as 'need-repro-project'. If an issue has not received a response in 2 days, it will be closed.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Adds two new GitHub Actions workflows to automatically manage and close inactive issues based on specific labels and timeframes.

CI:

• Introduces a workflow that checks for issues labeled as 'inactive' and closes them if they haven't received a response in 3 days.
• Introduces a workflow that checks for issues labeled as 'need-repro-project' and closes them if they haven't received a response in 2 days.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces two new GitHub Actions workflows to automate the process of checking for inactivity and closing issues that require a response but have not received one within a specified timeframe. The first workflow checks for issues labeled as 'inactive' and 'invalid', closing them after 3 days of inactivity. The second workflow closes issues labeled as 'need-repro-project' after 2 days of inactivity.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added a new workflow to check for inactive issues and close them if they are labeled as 'invalid' and have not received a response in 3 days.	Configured the workflow to run every 15 days. Utilized the actions-cool/issues-helper@v3 action to check for inactive issues. Set the inactive-label to 'inactive'. Set the inactive-day to 3. Added a body message to be posted when closing the issue.	.github/workflows/issue-check-inactive.yml
Added a new workflow to close issues that are labeled as 'need-repro-project' and have not received a response in 2 days.	Configured the workflow to run daily at 10 AM. Utilized the actions-cool/issues-helper@v3 action to close issues. Set the labels to 'need-repro-project'. Set the inactive-day to 2. Added a body message to be posted when closing the issue.	.github/workflows/issue-close-required.yml

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#5687	Add a GitHub Action to automatically close issues labeled as 'need-repro-project' after a period of inactivity.	✅
#5687	Add a GitHub Action to automatically close issues labeled as 'invalid' after a period of inactivity.	✅

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @ArgoZhang - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using a single workflow with different configurations to avoid code duplication.
• It might be helpful to add a comment to the issue before closing it, explaining why it's being closed and how to reopen it if needed.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (593a411) to head (112792d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5688   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          654       654           
  Lines        29689     29689           
  Branches      4213      4213           
=========================================
  Hits         29689     29689           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.