Add a public-endpoint-backed `vercel project access-groups` subcommand to list project access groups with table and JSON output, plus search/limit pagination options and telemetry coverage.

Made-with: Cursor

…ts from the paginated `/v2/teams/{teamId}/members` API endpoint, silently returning incomplete member lists for teams with more than ~20 members.

This commit fixes the issue reported at packages/cli/src/commands/teams/members.ts:62

## Bug Analysis

The `/v2/teams/{teamId}/members` Vercel API endpoint returns paginated results (consistent with all v2 API endpoints in the codebase). However, the `members.ts` implementation makes a bare request without any pagination query parameters (`limit`, `next`) and doesn't inspect the `pagination` field of the response.

This means:
1. For teams with more than ~20 members, the command only shows the first page of results
2. There is no indication to the user that more members exist
3. The `TeamMembersResponse` interface didn't even include the `pagination` field, so the data was being discarded

This is evident by comparing with the sibling `teams ls` command (`list.ts`), which:
- Accepts a `--next` flag via `nextOption` in its subcommand definition
- Passes `limit` and `next` query parameters to the API
- Displays a "To display the next page run..." hint when `pagination?.count === 20`

## Fix

The fix follows the exact same pagination pattern used by `teams ls`:

1. **`command.ts`**: Added `nextOption` to `membersSubcommand.options` array (it was already imported in the file for `listSubcommand`), and added a pagination example.

2. **`members.ts`**:
   - Added imports for `packageName`, `getCommandFlags`, and `cmd` (same imports used in `list.ts`)
   - Updated `TeamMembersResponse` interface to include the `pagination` field with `count`, `next`, and `prev`
   - Parses the `--next` flag from arguments
   - Validates that `--next` is an integer (same validation as `list.ts`)
   - Constructs a `URLSearchParams` with `limit=20` and optionally `next` for the API call
   - After rendering the table, checks if `pagination?.count === 20` and displays a "next page" hint command
   - For JSON output, includes `pagination` in the response so programmatic consumers can paginate

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: brookemosby <[email protected]>

Snapshots expected the pre-members help layout; adding members widens the
command column and includes the new subcommand in the teams help output.

Made-with: Cursor

Made-with: Cursor

… --yes

- Read-only project subcommands resolve link via getLinkedProject only in NI
  mode; emit link_required JSON with next steps instead of confirmation_required.
- Add LinkRequiredError and exitWithNonInteractiveError handling (project_not_found,
  link_required, argv --non-interactive, variant-specific next commands).
- inputProject: return unambiguous auto-detected project when nonInteractive.
- linkFolderToProject: skip env pull prompt when client.nonInteractive.
- Add and extend unit tests.

Made-with: Cursor

…error

outputAgentError calls process.exit(1), which Vitest flags as unexpected when
the test expects a returned exit code. Align with project members/access-groups
tests by spying on process.exit and asserting rejects with exit:1 plus JSON payload.

Made-with: Cursor