List the person's projects in the agent's account
Follow-up to #915, which merged before this last review fix landed.
When the agent can't list its own projects, the basecamp-connect skill falls back to listing the person's projects with their login. That login can default to a different account than the agent's, and connector setup reads projects in the agent's bound account. For someone in more than one account, the serve-all default could then pick projects from the wrong account, and setup would fail.
The fallback now passes --account with the account_id the agent's auth status reports. The skill already does the same when it reads the operator's name, for the same reason.
From Copilot's review of #915 at 36a232bb, "Pin fallback project listing to the agent's bound account".
bin/ci passes.
Summary by cubic
Fixes the basecamp-connect skill's fallback project listing so it scopes to the agent's bound account. When the agent can't list its own projects, the fallback lists the person's projects with their login, which can default to a different account and break connector setup for people in multiple accounts. The fallback now passes --account with the account_id that the agent's auth status reports, matching what the skill already does when reading the operator's name.