EP Merge: Fix issue with get pending contentions 204

[dfitchett]

What was the problem?

A bug has been observed in production which occurs when the pending claim returned a 204 on getting the contentions. This 204 resulted in the merge job failing due to 204 not being an acceptable status of that request, even tho the contentions from the EP400 could have been moved over successfully.

Associated tickets or Slack threads:

• 2998

How does this fix it?[^1]

Allows 204s on the request to get contentions for the pending claim.

How to test this PR

• pull code
• Unit Test:
  • from /domain-ee/ee-ep-merge-app run pytest
• Integration Tests:
  • run base platform
  • from /domain-ee/ee-ep-merge-app run pytest ./integration
• End to End tests:
  • run this CI action to verify successful integration test
  • run end to end tests locally:
  • export BIP_CLAIM_URL=mock-bip-claims-api:20300
  • run bgs and bip services and mocks:
    • COMPOSE_PROFILES="bip,bgs" ./gradlew :app:dockerComposeUp
    • COMPOSE_PROFILES="bip,bgs" ./gradlew -p mocks :dockerComposeUp
  • ./gradlew :domain-ee:ee-ep-merge-app:endToEndTest

[^1]: Pull-Requests guidelines. If PR is significant, update Current Software State wiki page. [^secrel]: To check if a PR will succeed in the SecRel workflow, test PRs in the SecRel pipeline.

[github-actions[bot]]

Test Results

109 tests  ±0   109 :white_check_mark: ±0   35s :stopwatch: +2s  33 suites ±0     0 :zzz: ±0   33 files   ±0     0 :x: ±0 

Results for commit 3277e85e. ± Comparison against base commit e4a06e13.

:recycle: This comment has been updated with latest results.

[github-actions[bot]]

JaCoCo Test Coverage

Overall Project	65.29%	:x:

There is no coverage information present for the Files changed