Set up new Bugsnag projects with the right type and team

**Objective:** Create the Bugsnag project `{project-name}` of platform type `{project-type}` and give `{collaborator-names}` access to it. This prompt changes data.

**Step 1: Check it does not already exist**

Call `bugsnag-get-project` with `name.contains` set to `{project-name}`. If a project of that name already exists, report it and stop. If something close exists, show it and ask before creating a near-duplicate.

**Step 2: Confirm the platform type**

`{project-type}` is the Bugsnag platform identifier, for example js, node, rails, android or ios. Call `bugsnag-get-project` and look at the `type` values already in use to confirm the spelling. If `{project-type}` does not look like one of them, ask before creating.

**Step 3: Create the project**

Call `bugsnag-add-project` with `name` set to `{project-name}` and `type` set to the confirmed type. Then call `bugsnag-get-project` again to read back the new `project-id`.

**Step 4: Grant access**

For each name in `{collaborator-names}`, call `bugsnag-get-collaborator` with `name.contains` to resolve the `collaborator-id`, then call `bugsnag-add-project-collaborator` with the new `project-id` and that id. Report anyone who could not be resolved instead of guessing.

**Step 5: Report**

Give the new project's name, type, id and its Bugsnag URL, who was granted access, and anyone who was not and why.

**Rules & Guidelines:**

* Confirm the project name and type with the user before Step 3. A project cannot be deleted through these tools.
* Resolve every collaborator by a read first. Never pass a guessed collaborator id.
* Do not call `bugsnag-update-project` to fix a name you typed wrongly without telling the user what happened.

**Validation:**

* If the create fails, stop. Do not attempt to grant access to a project that does not exist.
* If `{collaborator-names}` is empty, create the project and say that nobody was granted access yet.