[infra] Use a modified no-response workflow in flutter/packages

[elliette]

Resolves flutter/flutter#191756

Allows us to use the waiting for response label on PRs. PRs with that label will be auto-closed after 21 days of no response.

Copies the existing flutter/flutter no-response.yaml and no-response.js files to flutter/packages, but removes all the issue-specific logic since issues are disabled on flutter/packages so we only need this to work for PRs.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

Test exemption: Github workflow change.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request introduces a new GitHub Actions script, .github/scripts/no-response.js, which automates the closure of inactive pull requests labeled 'waiting for response' after 21 days. Feedback on this implementation suggests optimizing API usage by setting per_page: 100 across all paginated requests to prevent rate limiting. Additionally, the feedback recommends using optional chaining to safeguard against runtime errors when accessing nested properties of events and commits, and addressing a potential bug where deleted users could falsely trigger response detection.

[tarrinneal]

seems good :)

[tarrinneal]

I don't know what the norm is for our cron length for this type of thing, but I feel like every 15 minutes is a bit more than necessary. nbd probably

[elliette]

Bumped to every 30 mins. 15 is what flutter/flutter is currently using for this label, we can switch down to 15 if the lag between when a contributor responds on a PR and when the label is removed is too slow.

[auto-submit]

autosubmit label was removed for flutter/packages/12745, because - The status or check suite Dashboard Checks has failed. Please fix the issues identified (or deflake) before re-applying this label.