API-39291 Add log lines

[acovrig]

Summary

• Add 2 log lines to aid in troubleshooting

Related issue(s)

• API-39291

Testing done

• rspec

What areas of the site does it impact?

MPI profile lookups (v1 calls)

Acceptance criteria

• [ ] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• [ ] No error nor warning in the console.
• [ ] Events are being sent to the appropriate logging solution
• [ ] Documentation has been updated (link to documentation)
• [ ] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• [ ] Feature/bug has a monitor built into Datadog (if applicable)
• [ ] If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• [ ] I added a screenshot of the developed feature

[acovrig]

Why are we adding a ClaimsApi specific logger to the general MPI class? Can you describe your needs with the logs here? Trying to see if something already exists, or if we can add something sensible that everything can leverage and isn't specific to ClaimsApi

@bosawt We're troubleshooting an error (DD logs) with MPI's response. The goal is to see if we see both unable_to_locate_mpi_record log lines together and hopefully get more insight to the root issue.

On a side note, I am unsure what e.message could be (I.E. if it could contain PII) so I opted not to log e.message - If you know it wouldn't have PII, I'd love to log it.