Add table for motor stop and airmode combination

[haslinghuis]

• closes The relation between MOTOR_STOP and AIRMODE should be better documented betaflight#14231

This pull request includes a small change to the docs/wiki/configurator/motors-tab.md file. The change adds a new table to clarify the behavior of motors when armed under different configurations of AIRMODE and Motor Stop settings.

Changes to docs/wiki/configurator/motors-tab.md:

• Added a table describing motor behavior when armed under different configurations of AIRMODE and Motor Stop settings.

[netlify]

✅ Deploy Preview for origin-betaflight-com ready!

Name	Link
🔨 Latest commit	01b693c
🔍 Latest deploy log	https://app.netlify.com/sites/origin-betaflight-com/deploys/679f9fbb15936200081f4e4c
😎 Deploy Preview	https://deploy-preview-518.dev.web.betaflight.com
📱 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 site configuration.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dmak]

Maybe the text needs some rewording (sorry, the idea came just now):

"Motor Stop" → "MOTOR_STOP"

Let me brush it up a bit:

| **Scenario**                                     | **Motors' behavior when armed**                           |
|--------------------------------------------------|-----------------------------------------------------------|
| `AIRMODE` is disabled & `MOTOR_STOP` is enabled  | Motors **stay off** until throttle is raised.             |
| `AIRMODE` is disabled & `MOTOR_STOP` is disabled | Motors **spin at idle speed** when armed.                 |
| `AIRMODE` is enabled                             | Motors **always spin** when armed, even at zero throttle. |

⚠️ The table needs validation ⚠️

But in combination with PR #4326 it probably does not make much sense, as if AIRMODE is enabled then MOTOR_STOP is hidden. Probably more relevant for older versions of BF?

[nerdCopter]

In this hobby pilots eventually learn when and what happens. This scenario is akin to when motor-pwm-frequency was still shown, but only applicable if analog protocols were in use. Eventually newcomers want clarification and UI changes so it becomes as such; however, the underlying settings can still exist in CLI.

You are welcome to make a PR to clarify variable names and bold-faces if you feel it necessary.