Copy a Ghost Inspector test to staging without touching the original

**Objective:** Make a copy of the Ghost Inspector test named `{test-name}`, name the copy `{new-name}`, and point it at `{new-start-url}` and browser `{new-browser}` where those were given.

**Step 1: Identify the source test**

Call `ghost-inspector-get-test` with `name.contains` set to `{test-name}`. If more than one matches, list the matches with their suite, browser and start url and stop; copying the wrong test leaves clutter someone has to clean up. Keep the `id`, `start-url`, `browser`, `region` and `suite-name`.

**Step 2: Check the new name is free**

Call `ghost-inspector-get-test` with `name.contains` set to `{new-name}`. If a test by that name already exists, report it and stop; the user either meant to update that one or needs a different name.

**Step 3: Confirm the plan**

Show the user: the source test and its suite, the name the copy will take, and each setting that will change, old value to new value. Say plainly that the copy lands in the same suite as the original and will run on that suite's schedule. Ask for confirmation, and do not continue without an explicit yes.

**Step 4: Duplicate**

Call `ghost-inspector-duplicate-test` with `test-id` from step 1. Call it exactly once. Keep the `id` it returns, that is the new test. If it does not return an id, report the failure and stop; do not call it again, since a retry risks leaving two copies behind.

**Step 5: Retarget the copy**

Call `ghost-inspector-update-test` with `test-id` set to the NEW id from step 4, never the source id, and set `name` to `{new-name}` plus `start-url` and `browser` only where those parameters were supplied. Call it exactly once.

**Step 6: Verify and report**

Call `ghost-inspector-get-test` with `id` set to the new id and confirm the name, start url and browser are what was asked for. Report the new test's id, name, suite and settings, and state that the original is unchanged. Do not run the copy; say that a first run can be done with the rerun prompt once the user is ready.

**Rules and guidelines:**

* Only `ghost-inspector-duplicate-test` and `ghost-inspector-update-test` may write, once each, after the confirmation in step 3, and `ghost-inspector-update-test` may only ever be given the new test id.
* Do NOT call `ghost-inspector-execute-test`, `ghost-inspector-execute-suite`, `ghost-inspector-execute-on-demand-test`, `ghost-inspector-duplicate-suite`, `ghost-inspector-create-suite` or `ghost-inspector-update-suite`.
* If step 5 fails, say so explicitly and report the new test's id, because the copy exists and still carries the original settings.

**Validation:**

* If `{test-name}` matches nothing, list some test names and stop.
* If `{new-name}` is empty, ask for it and stop rather than leaving a copy called the same as the original.
* If the user declines the confirmation, stop without writing.