I'd like to create new environment via CLI and I'm having issues with authentication.

If I use existing project token that is scoped to a staging environment, I can't create new environment as I get an error
```

Failed to get environments: Not Authorized: {"response":{"errors":[{"message":"Not Authorized","locations":[{"line":2,"column":3}],"path":["environments"],"extensions":{"code":"INTERNAL_SERVER_ERROR"},"traceId":"5831592547172749352"}],"data":null,"status":200,"headers":{}},"request":{"query":"query GetEnvironments($projectId: String!) {\n environments(projectId: $projectId) {\n edges {\n node {\n id\n name\n deployments {\n edges {\n node {\n id\n status\n }\n }\n }\n serviceInstances {\n edges {\n node {\n id\n domains {\n serviceDomains {\n domain\n id\n }\n }\n serviceId\n }\n }\n }\n }\n }\n }\n}","variables":{"projectId":"53e4391c-546e-4e1f-89ec-0c07af6f0fa4"}}}
```

If I use account token scoped to the team, I get error Project Token not found

If I login to Railway CLI via railway login, I can create new environment but that flow isn't an option since we are going to be creating new environments in scripted environment (in CI pipeline). We need ability to use RAILWAY_TOKEN= variable.