Agentic Workflow: Check tool repo for issue triage

[edvilme]

This pull request updates two GitHub Actions workflow lock files to improve automation and compatibility. The major changes include broadening domain allowlists for network access, reverting to earlier versions of certain actions for stability, and expanding the issue triage workflow to handle both new issues and issue comments. Naming and descriptions have also been updated for clarity.

Workflow compatibility and security improvements

• Expanded the list of allowed domains for network access in both .github/workflows/check-python-versions.lock.yml and .github/workflows/issue-check-template.lock.yml to include additional package, security, and validation endpoints. This ensures workflows can access all necessary resources and improves reliability. [1] [2]
• Reverted the github/gh-aw/actions/setup action from version v0.49.6 to v0.47.5 in both workflows, likely to address compatibility or stability issues. [1] [2] [3] [4] [5] [6] [7] [8] [9]
• Changed actions/download-artifact from version v7.0.0 to v6 throughout both workflows for improved compatibility. [1] [2] [3] [4] [5] [6] [7] [8]

Issue triage workflow enhancements

• Expanded the workflow trigger in .github/workflows/issue-check-template.lock.yml to run not only on new issues, but also when a maintainer comments /triage-issue on an existing issue, and added logic to search for related issues in the upstream isort repository.
• Updated workflow naming from "Issue Root-Cause & Template Check" to "Issue Triage" and revised descriptions for clarity and accuracy in multiple places. [1] [2] [3] [4] [5] [6] [7]

These changes collectively improve workflow robustness, clarity, and ensure the automation can handle a wider range of issue triage scenarios.

[rchiodo]

Approved via Review Center.