Deploy: pulling with an invalid project id returns a bad error

openfn pull abc

abc is not a valid project id (it's not a UUID). So I get error output like this:

[CLI] ♦ Downloading existing project state (as JSON) from the server.
Checking https://app.staging.openfn.org/api/provision/abc? for existing project.

[CLI] ✘ Command failed!
[CLI] ✘ Error: Failed to fetch project abc: Bad Request
    at getProject (file:///home/joe/.asdf/installs/nodejs/18.12.1/lib/node_modules/@openfn/cli/node_modules/@openfn/deploy/dist/index.js:694:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async pullHandler (file:///home/joe/.asdf/installs/nodejs/18.12.1/lib/node_modules/@openfn/cli/dist/process/runner.js:1554:31)
    at async parse (file:///home/joe/.asdf/installs/nodejs/18.12.1/lib/node_modules/@openfn/cli/dist/process/runner.js:1778:12)

This is not a useful error message. We should do better in the CLI at helping the user understand the actual problem. I think Lightning could probably be more helpful about this too (although I can't see the error body so I don't know, maybe there's a good message attached).

We also shouldn't be logging a stack trace for an error like this. It doesn't help the user.

Start by reproducing openfn pull abc and trace the pullHandler path in @openfn/cli through the getProject call in @openfn/deploy. Done means an invalid project ID produces a clear explanation of the validation problem and does not print a stack trace.