fix: correct client test case description

[mdb]

Description

This corrects the it() description associated with the PagerDuty API client's handling of generic non-OK HTTP responses that are not 401s, 403s, or 404s. Previously, the test case claimed the client throws NotFoundErrors in such cases. This is not true; the client throws a generic descriptive error in such cases.

Thanks!

Issue number: (e.g. #123)

Type of change

• [ ] New feature (non-breaking change which adds functionality)
• [x] Fix (non-breaking change which fixes an issue)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• [X] I have performed a self-review of this change
• [X] Changes have been tested
• [X] Changes are documented
• [X] Changes generate no new warnings
• [X] PR title follows conventional commit semantics

If this is a breaking change 👇

• [ ] I have documented the migration process
• [ ] I have implemented necessary warnings (if it can live side by side)

Acknowledgement

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.