Fix CapabilityStatement conformance for resources

[v-rachitsh]

Summary

Fixes #5394. External PR #5473

In STU3, CapabilityStatement.rest.resource.interaction has a minimum cardinality of 1 (spec). Resources like Parameters that are explicitly excluded from interaction population (line 303-307) were still appearing in the resource list with an empty interaction array, causing FHIR-conformant parsers (e.g., Firely SDK 6.x with strict validation) to reject the CapabilityStatement.

Changes

• In CapabilityStatementBuilder.Build(), added a cleanup step that removes resource entries with no interactions before serialization
• This ensures the output CapabilityStatement conforms to the FHIR standard across all versions

Why this approach

Rather than modifying how Parameters is handled specifically, this cleanup catches any resource that ends up with zero interactions — making it robust against future edge cases. The comment explains the STU3 cardinality requirement for maintainability.

Related issues

AB#191808

Testing

Describe how this change was tested.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.93%. Comparing base (abca618) to head (448d061).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5617      +/-   ##
==========================================
+ Coverage   76.90%   76.93%   +0.02%     
==========================================
  Files         997      997              
  Lines       36616    36622       +6     
  Branches     5529     5533       +4     
==========================================
+ Hits        28160    28175      +15     
+ Misses       7104     7095       -9     
  Partials     1352     1352              

see 11 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.