Return problem detail when LCP fulfillment fails (PP-1641)

[jonathangreen]

Description

If LCP fulfillment request does not return a status in the 2xx range, raise a ProblemDetailException, which will be returned to the clients.

Motivation and Context

We've seen a number of times recently when LCP fulfillment fails, and the CM just blindly passes along whatever the LCP API gives us, which confuses the apps. Instead in this PR if we get an unexpected status code, we turn that into a problem detail, and log the issue. This should give a better user experience and let us track down the problems from our logs.

This PR is only a couple lines, but it took a lot of refactoring in #2034 and #2035 to get here.

How Has This Been Tested?

• Tested locally

Checklist

• I have updated the documentation accordingly.
• All new and existing tests passed.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.75%. Comparing base (5fb1411) to head (ba24269).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2033   +/-   ##
=======================================
  Coverage   90.75%   90.75%           
=======================================
  Files         342      342           
  Lines       40516    40516           
  Branches     8771     8771           
=======================================
  Hits        36772    36772           
  Misses       2486     2486           
  Partials     1258     1258           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tdilauro]

🏁