vercel inspect fails with 'Not authorized' when using team scope token

## Description

When deploying with `--prebuilt` using a team-scoped token, the deploy itself succeeds but the subsequent `vercel inspect` call fails with:

```
Error: Not authorized: Trying to access resource under scope "minsu-lees-projects-b1e388b7".
You must re-authenticate to this scope or use a token with access to this scope.
```

## Steps to Reproduce

1. Set up vercel-action with a team-scoped token and `VERCEL_ORG_ID` / `VERCEL_PROJECT_ID`
2. Use `vercel-args: '--prebuilt'`
3. Deploy succeeds, but the inspect step after deploy fails

## Workflow Configuration

```yaml
- uses: amondnet/vercel-action@v25
with:
vercel-token: ${{ secrets.ORG_VERCEL_TOKEN }}
github-token: ${{ secrets.GITHUB_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
vercel-version: '50.22.1'
vercel-args: '--prebuilt'
```

## CI Log

```
set env variable : VERCEL_ORG_ID
set env variable : VERCEL_PROJECT_ID
npx vercel@50.22.1 --prebuilt -t *** ...
Vercel CLI 50.22.1
Deploying ***/hub-web
Preview: https://hub-xxx.vercel.app [38s]
To deploy to production, run `vercel --prod`

set preview-url output
npx vercel@50.22.1 inspect https://hub-xxx.vercel.app -t ***
Vercel CLI 50.22.1
Error: Not authorized: Trying to access resource under scope "minsu-lees-projects-b1e388b7".
```

## Expected Behavior

`vercel inspect` should use the same `VERCEL_ORG_ID` scope as the deploy command, or pass `--scope` to the inspect call.

## Environment

- vercel-action: v25
- vercel-version: 50.22.1
- Runner: self-hosted Linux x64