[LungMAP] Separate Summary Mapping by Configuration

[frano-m]

Currently, summary mapping logic is shared across configurations via common constants and mappers (e.g., SUMMARIES, BIND_SUMMARY_RESPONSE). This approach limits flexibility and makes it difficult to support configuration-specific summary shapes or display logic.

Task

Refactor the summary mapping so that each configuration (e.g., LungMAP) defines its own summary response shape and mapping logic.
Move summary mapping logic out of shared constants and into configuration-specific files (such as each config’s summaryViewModelBuilder).
Ensure that each configuration can independently define how its summary response is parsed and displayed, without relying on shared summary constants or mappers.

DOD

LungMAP configuration has its own summary response type and mapping function.
No references to shared summary constants (e.g., SUMMARIES, BIND_SUMMARY_RESPONSE) remain in the summary mapping code path.
The summary display logic is fully decoupled between configurations.