feat(RECAPDocument): Validate attachment number against document type

[elisa-a-v]

Resolves #3982

This PR adds a model-wide validation for the RECAPDocument model that checks that:

• If the doc is a main PACER doc, no attachment number is provided
• If the doc is an attachment, an attachment number is provided

It also fixes an issue where previously empty RECAPDocuments didn't have their document_type updated, so if the rd was an attachment, the attachment number was added but the document type remained as a main PACER document. We now update the document type every time, so this should not happen again.

Given the nature of the changes, we're now logging errors in several places for future troubleshooting, and a new sentry setting was added which enables attaching the entire stack trace to sentry logs.

this also adds tests and updates docs to reflect changes.

[sentry-io[bot]]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ attachment_number must be null for a main PACER document. /api/rest/{version}/recap/ View Issue
• ‼️ ValidationError: {'attachment_number': ['attachment_number must be null for a main PACER document.']} cl.corpus_importer.tasks.upload_pdf_to_ia View Issue
• ‼️ attachment_number must be null for a main PACER document. cl.corpus_importer.tasks.upload_pdf_to_ia View Issue

_{Did you find this useful? React with a 👍 or 👎}