Enforce strict limits when forming the probable bounds message

[woodwoerk]

Description

Previously, if a measure had a strict limit (e.g. minValue) and a suggested limit (e.g. probableLowerBound), and the suggested limit was higher/ lower than the strict limit, it was incorrectly used in the message. Fix this so that the strict bounds are considered when forming the message.

---

✅ Pre-Merge Checklist

Type of Change

• Set the PR's label to match the nature of this change

Testing

• Built Unit tests (unit tests added/updated)
• [-] Authorization is tested (permissions and access controls verified)
• [-] Mobile screen widths tested for responsiveness (if applicable)
• Manually tested locally in all affected projects (functionality verified)

  Manual testing instructions

  If feature requires manual testing by reviewer, you can provide instructions here.

Internationalization & Accessibility

• [-] Accessibility standards met (WCAG compliance, screen reader support)

Dependencies

• [-] Dependencies are merged (if applicable. If the change depends on other PRs)

[lilia1891]

molto buono!