[LH Doc Upload] Improve BDD production monitoring

[NB28VT]

After we have launched the BDD Instructions migration with the basic production monitor, we need to add a few more features to consider it truly complete:

• [x] Log both submitted_claim_id and the Form526Submission primary key id in the api providers, we are only doing the first one at the moment

• [ ] Incorporate the polling metrics that were added in https://github.com/department-of-veterans-affairs/va.gov-team/issues/95603

[ajones446]

Unless something changes by the time we get to this task, the ZSF criteria can be removed. Github issue conversation from 10/23: https://github.com/department-of-veterans-affairs/va.gov-team/issues/91269#issuecomment-2433375331

[NB28VT]

@ajones446 @kylesoskin FYI I'm removing this item from the acceptance criteria for adding alert monitors to the BDD release dashboard as @freeheeling 's work on the ZSF compliance would make creating and maintaining these monitors redundant. Agree?

"Add alert monitors and set them up to warn us in the correct Slack channel as was done in the failure email dashboard."

Ditto for "For monitors, tag them “service:disability-application” (DataDog standards slack 7/24 )"

[NB28VT]

PRed the first item here https://github.com/department-of-veterans-affairs/vets-api/pull/19217

[NB28VT]

Logging fixes for item 1 completed in https://github.com/department-of-veterans-affairs/vets-api/pull/19217