Simplify use of reqwest a bit

[jwiegley]

No description provided.

[ghost]

We currently get a bare Reqwest error if you use dfx when the client isn't running:

» dfx canister call hello '("Stanley")'
An error occured:
Reqwest(
    Error(
        Hyper(
            Error(
                Connect,
                Os {
                    code: 61,
                    kind: ConnectionRefused,
                    message: "Connection refused",
                },
            ),
        ),
        "http://127.0.0.1:8000/api/v1/submit",
    ),
)

Should I file this as a separate concern? Or does it make sense to throw in here, since you're already touched Reqwest error messages?

[lsgunnlsgunn]

My .02, please wrap this is a nicer error message, if possible. To me and to at least one member of the community "Reqwest" looks like an Elmer Fudd impression (AKA, a typo).

(I have learned that is it legit, but it looks sort of unprofessional if you don't know that.)

[jwiegley]

@stanleygjones Improved error handling is much better split off as a separate concern, since I don't have the time to make that fix, and I doubt @hansl will want to work on top of my PR.

[hansl]

We have a separate ticket for improved error handling.

[hansl]

Approving this as it's a good cleanup. Next step would be to have async/await.

[jwiegley]

Yes, async/await will make this module beautifully clear.