log vet360 request bodies

[lihanli]

Description of change

we're seeing errors with the vets360 api possibly related to the effective_start_date attribute, we should log the requests to help figure out what is causing these errors

Testing done

automated tests

Testing planned

test in staging

Applies to all PRs

• Appropriate logging
• Swagger docs have been updated, if applicable
• Provide link to originating GitHub issue, or connected to it via ZenHub
• Does not contain any sensitive information (i.e. PII/credentials/internal URLs/etc., in logging, hardcoded, or in specs)
• Provide which alerts would indicate a problem with this functionality (if applicable)

[annaswims]

This is a whole lot of PII to be logging. Could we log just the few attributes we're interested in?

[kfrz]

Is there no way to recreate this in a lower environment or on the command line rather than capturing all the body? Is there an associated issue or further details?

[lihanli]

@kfrz here's the issue for the error https://github.com/department-of-veterans-affairs/vets.gov-team/issues/19386

i tried to recreate the error in console but it didn't work (the request succeeded and returned 200)

[lihanli]

@annaswims i changed it to only log the dates

[annaswims]

LGTM! Thanks for making the change!