Fixes for maximum stage complexity calculation

[vmiura]

This change helps to address an issue with scoring when tests reach the maximum complexity that a story supports. Currently this only applies to the "Multiply" test among the mainline tests.

For the following screenshots, I've artificially limited the "Multiply" test's totalRows to 10 (for a maximum stage complexity of 135) highlight this issue.

When a test reaches the maximum stage complexity, the controller can try to test a much higher complexity than the stage supports, since the code estimating the maximum complexity isn't aware of the stage's limit. This is particularly an issue for the Slope Profile, which has a harder time calculating the score when all samples are basically in a flat line.

Before

Slope Profile

After

Slope Profile

Note: the Slope score being less than 135 in the "After" picture isn't because of this change. The Slope regression is hit & miss either way, but is generally more predictable after this change. The Mean ramp score is pretty noisy with the Slope function as we can see.

Windowed Strict Profile

For the Windowed Strict profile, the score is generally more accurate with or without this change.

[netlify[bot]]

✅ Deploy Preview for webkit-motionmark-preview ready!

Name	Link
🔨 Latest commit	7057bc1a1c9941f30c1ed85bda4dc6bd66a5deb7
🔍 Latest deploy log	https://app.netlify.com/projects/webkit-motionmark-preview/deploys/689296cf9be4060008d3d539
😎 Deploy Preview	https://deploy-preview-90--webkit-motionmark-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.