Fixed #613 Added response status code to verbose log message.

[danielmorell]

Description of the change

This resolves issue #613 by adding the response status code from the API to the verbose log, if there is an error response status.

I also updated the associated test. Instead of posting to a non-existent endpoint, I sent an invalid access token. This seems more deterministic since we don't just want an error, we want a specific status code.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Maintenance
• New release

Related issues

• Fix Add status code to failed API send verbose log. #613

Checklists

Development

• Lint rules pass locally
• The code changed/added as part of this pull request has been covered with tests
• All tests related to the changed code pass in development

Code review

• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
• "Ready for review" label attached to the PR and reviewers assigned
• Issue from task tracker has a link to this pull request
• Changes have been reviewed by at least one other engineer