Updates logging to include how the contention is classified

[tyler-spangler6]

What was the problem?

During the classification process, a claim for increase can either be classified using the diagnostic code or the contention text. Our logging only included if the contention was classified, but not how the contention was classified. This is important for us to know to be able to track diagnostic codes that we do not have mapped that we are able to classify via contention text. It can also help us add new Diagnostic Codes that are being sent to the service to help cover more increase contentions.

The example of the new logging is below:

• If the contention is classified by diagnostic code:

{
    "vagov_claim_id": 100,
    "claim_type": "claim_for_increase",
    "classification_code": 8940,
    "classification_name": "Cancer - Musculoskeletal - Other",
    "contention_text": "unmapped contention text",
    "diagnostic_code": 5012,
    "is_in_dropdown": false,
    "is_lookup_table_match": true,
    "is_multi_contention": true,
    "endpoint": "/expanded-contention-classification",
    "classification_method": "diagnostic_code",
    "processed_contention_text": null,
    "date": "2025-01-02 10:09:02",
    "level": "info"
}

• If the contention is classified by contention text:

{
    "vagov_claim_id": 100,
    "claim_type": "claim_for_increase",
    "classification_code": 8997,
    "classification_name": "Musculoskeletal, knee",
    "contention_text": "unmapped contention text [acl tear]",
    "diagnostic_code": 1234,
    "is_in_dropdown": false,
    "is_lookup_table_match": true,
    "is_multi_contention": true,
    "endpoint": "/expanded-contention-classification",
    "classification_method": "contention_text",
    "processed_contention_text": null,
    "date": "2025-01-02 10:09:02",
    "level": "info"
}

• If the contention is not classified by either:
  {
  "vagov_claim_id": 100,
  "claim_type": "claim_for_increase",
  "classification_code": null,
  "classification_name": null
  "contention_text": "unmapped contention text",
  "diagnostic_code": 1234,
  "is_in_dropdown": false,
  "is_lookup_table_match": true,
  "is_multi_contention": true,
  "endpoint": "/expanded-contention-classification",
  "classification_method": "unmapped_contention",
  "processed_contention_text": null,
  "date": "2025-01-02 10:09:02",
  "level": "info"
  }

Associated tickets or Slack threads:

• https://github.com/orgs/department-of-veterans-affairs/projects/873/views/2?pane=issue&itemId=92216602&issue=department-of-veterans-affairs%7Cvagov-claim-classification%7C666

How does this fix it?¹

How to test this PR

• Unit tests are written to cover the logic of creating the field and that it is incorporated in the logs.

Footnotes

1. Pull-Requests guidelines. If PR is significant, update Current Software State wiki page. ↩

[github-actions]

Test Results

102 tests  ±0   102 ✅ ±0   17s ⏱️ -1s
 31 suites ±0     0 💤 ±0 
 31 files   ±0     0 ❌ ±0 

Results for commit 0cc39ee. ± Comparison against base commit ff4e1cb.

♻️ This comment has been updated with latest results.

[github-actions]

JaCoCo Test Coverage

Overall Project	68%	❌

There is no coverage information present for the Files changed

[williamphelps13]

LGTM!