Fix microbatch model PartialSuccess status to result in non-zero exit code

[QMalcolm]

Resolves #11114

Problem

If run microbatch model resulted in a partial success, it didn't guarantee that there'd be a non-zero exit code, and this was problematic

Solution

Update the interpret_results method to include PartialSuccess as being a failure state

Checklist

• I have read the contributing guide and understand what's expected of me.
• I have run this code in development, and it appears to resolve the stated issue.
• This PR includes tests, or tests are not required or relevant for this PR.
• This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
• This PR includes type annotations for new and modified functions.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.90%. Comparing base (03fdb4c) to head (ad566ba).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11115      +/-   ##
==========================================
- Coverage   88.96%   88.90%   -0.06%     
==========================================
  Files         183      183              
  Lines       23933    23933              
==========================================
- Hits        21291    21278      -13     
- Misses       2642     2655      +13     

Flag	Coverage Δ
integration	86.20% <ø> (-0.14%)	⬇️
unit	61.96% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Unit Tests	61.96% <ø> (ø)
Integration Tests	86.20% <ø> (-0.14%)	⬇️

[ChenyuLInx]

LGTM