15223: generate empty in convert

[mkalish]

This PR updates the code so that when an empty report (or any situation where the number of items cannot be determined) makes it to the convert step.

Test Steps:
There are a integration tests that covers this, but as the pipeline is currently structured this is hard to test manually as the report function will synchronously fail.

Changes

• Adds a new trackEmptyReport that can be used anywhere in the pipeline
• Updates the convert step to use it if it cannot determine the number of items

Checklist

Testing

• Tested locally?
• Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
• (For Changes to /frontend-react/...) Ran npm run lint:write?
• Added tests?

Process

• Are there licensing issues with any new dependencies introduced?
• Includes a summary of what a code reviewer should test/verify?
• Updated the release notes?
• Database changes are submitted as a separate PR?
• DevOps team has been notified if PR requires ops support?

Linked Issues

• Support Generating an Empty Report in Convert Step #15223

To Be Done

Specific Security-related subjects a reviewer should pay specific attention to

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Manifest Files

[github-actions]

Test Results

1 239 tests  +2   1 235 ✅ +2   7m 47s ⏱️ +22s
  162 suites ±0       4 💤 ±0 
  162 files   ±0       0 ❌ ±0 

Results for commit 42e5870. ± Comparison against base commit 1333c99.

♻️ This comment has been updated with latest results.

[github-actions]

Integration Test Results

 53 files   53 suites   27m 38s ⏱️
410 tests 401 ✅ 9 💤 0 ❌
413 runs  404 ✅ 9 💤 0 ❌

Results for commit 42e5870.

♻️ This comment has been updated with latest results.

[thetaurean]

LGTM 👍 One small comment:

I wonder if there's any tech debt in ActionHistory.kt worth ticketing. I remember getting a little lost / confused when tracking a created empty report in other steps.

Separate but related, should we scope some tickets for using this new function in other places we generate an empty report (e.g. FHIRDestinationFilter.kt and FHIRReceiverFilter.kt)? Will spend a little more time thinking this over tomorrow.

[mkalish]

@thetaurean 100% think there are tech debt tickets to be made for action history but I have always been unsure where to start since I think there could be an argument to simply rewrite the whole thing.

For the other pipeline steps, maybe? This spot in in convert is a little unique in the sense that its only part of the pipeline where the number of items is unknown in case of an error

[sonarcloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud