Clarify pricing detail labels for applied modifiers

Price details in the charges flow should use plain-language labels that explain which condition actually changed the price, rather than technical or vague wording.

Examples from the discussion included entries like conditional met or rows that only say an amount was added to cost without naming the triggering rule, while other entries are clearer because they say things like based on square footage or age. The goal is to make pricing explanations understandable to office staff without needing prior knowledge of how pricing rules are configured.

Transcript Context

The team asked whether the hover/help details on pricing could be more explicit about what caused the charge change. A specific example was that some rows just say an amount was added, but do not say what condition was met. The feedback was that the system appears to already know which condition triggered, so that information should be surfaced more clearly.

This is separate from ATT-1724, which is about modifier details not displaying at all. This issue is about making the displayed explanations clearer once they are shown.