error logs running `aio app deploy` when using a console.json without logging into the org

### Expected Behaviour
After running `aio app use `, deploy should work regardless of login status in the org in developer console.
I have the correct information (runtime namespace and auth) in the `.env` file so that should be enough to successfully deploy.
```
$ aio app deploy
Using local project's @adobe/aio-cli-plugin-asset-compute version 2.0.1

✔ Built 1 action(s) for 'dx/asset-compute/worker/1'
ℹ no frontend or a build already exists, skipping frontend build for 'dx/asset-compute/worker/1'
✔ Deployed 2 action(s) for 'dx/asset-compute/worker/1'
no frontend, skipping frontend deploy 'dx/asset-compute/worker/1'
Your deployed actions:
web actions:
-> https://.adobeioruntime.net/api/v1/web/dx-asset-compute-worker-1/worker-ocr
non-web actions:
-> dx-asset-compute-worker-1/__secured_worker-ocr
New Extension Point(s) in Workspace 'Stage': 'dx/asset-compute/worker/1'
Successful deployment 🏄
```

### Actual Behaviour
I hit a bug accessing the extension points. ~It is unclear if the action had been deployed properly.~
I confirmed the action does still get deployed regardless of the error message. However, this error message should be hidden or not shown. It should show "successful deployment" to the user.
```
$ aio app deploy
Using local project's @adobe/aio-cli-plugin-asset-compute version 2.0.1

✔ Built 1 action(s) for 'dx/asset-compute/worker/1'
ℹ no frontend or a build already exists, skipping frontend build for 'dx/asset-compute/worker/1'
✔ Deployed 2 action(s) for 'dx/asset-compute/worker/1'
no frontend, skipping frontend deploy 'dx/asset-compute/worker/1'
Your deployed actions:
web actions:
-> https://704227-802ivoryhalibut-stage.adobeioruntime.net/api/v1/web/dx-asset-compute-worker-1/worker-ocr
non-web actions:
-> dx-asset-compute-worker-1/__secured_worker-ocr
⠇ Getting Extension Points in Workspace=Stage... › Error: [CoreConsoleAPISDK:ERROR_GET_WORKSPACE_ENDPOINTS] 451 - Unknown ("Use POST /console/services/ims/organizations/:orgId/terms API to accept developer terms for
› your org first. You can use GET /console/services/ims/terms to retrieve the current developer terms.")
```

### Reproduce Scenario (including but not limited to)
- anytime you try to deploy an app in an environment you are not logged into (after setting the context using `aio app use`

#### Steps to Reproduce
note: `a` and `b` are two different orgs

note: you are inside an app builder app

1. run `aio login` or login to an org `a` in the developer console ui
2. run `aio app deploy` (everything should work fine)
2. run `aio app use