Handle unexpected HTTP responses

[joshuaflanagan]

This will better handle the situation where the HTTP response body cannot be parsed as JSON. Instead of throwing a JsonException, we will throw a ShipEngineException containing the HttpResponseMessage. This will give the caller a chance to handle the response in their own way.

We will also try to include a request ID on all ShipeEngineException now - by pulling from the response header in cases where we don't get a ShipEngine Error JSON response.

[coveralls]

Pull Request Test Coverage Report for Build 9717752223

Details

• 8 of 8 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.9%) to 77.978%

---

Totals
Change from base Build 9714075367:	0.9%
Covered Lines:	654
Relevant Lines:	816

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 9718240694

Details

• 18 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+1.3%) to 78.418%

---

Totals
Change from base Build 9714075367:	1.3%
Covered Lines:	654
Relevant Lines:	813

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 9718822717

Details

• 32 of 32 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+2.3%) to 79.418%

---

Totals
Change from base Build 9714075367:	2.3%
Covered Lines:	657
Relevant Lines:	814

---

💛 - Coveralls