RM-72368 Release over_react_test 2.9.3 (Hotfix to fix prop type expectations)

[aaronlademann-wf]

Motivation

The logsPropError matcher that replaces the throwsPropError matcher had a typo in the message it expects from the logger. It is missing a period.

Changes

1. Add the missing period.
2. Update the tests so that the first and second argument are used - which is the only way the missing period would have caused a test failure.

Release Notes

Fix logsPropError matcher message expectation

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review: @greglittlefield-wf @joebingham-wk @corwinsheahan-wf

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Client Platform member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary3-wk]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[greglittlefield-wf]

+10

[aaronlademann-wf]

@Workiva/release-management-pp

[rmconsole-wf]

+1 from RM