Only warn about projects toolset when explicitly specified, not implied by "all"

[Copilot]

When users specify toolsets: [all], they get a warning about the projects toolset requiring organization permissions, even though they likely don't intend to use projects functionality. The warning should only appear when projects is explicitly mentioned.

Changes

Modified warning logic in pkg/workflow/compiler.go:

• Check original toolsets (before expansion) instead of expanded toolsets
• Warning now only triggers when projects is explicitly listed

# Shows warning
tools:
  github:
    toolsets: [projects]

# No warning (fixed)
tools:
  github:
    toolsets: [all]

Added test coverage:

• Tests for explicit projects usage (warns)
• Tests for implicit projects via "all" (no warning)
• Tests for default/other toolsets (no warning)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Using github: toolsets: [all] gives warning about projects toolset</issue_title>
<issue_description>
It's a bit confusing to the user that using

  github:
    toolsets: [all]  

causes this warning:

 The 'projects' toolset requires a GitHub token with organization Projects permissions.
ℹ See: https://githubnext.github.io/gh-aw/reference/tokens/#gh_aw_project_github_token-github-projects-v2

This is because "all" includes the projects toolset. While it's logically correct to give the warning - the implied "projects" toolset is indeed not going to work without the required token - it is very unlikely that with "all" the user is trying to do anything with projects.

I think we should only give this warning if the projects toolset is mentioned explicitly, not implied by "all".
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Using github: toolsets: [all] gives warning about projects toolset #11349

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.