feat(api): Differenciate motion settings between 96ch 200 and 1000

[ryanthecoder]

Overview

Hardware testing/lifetime has found that the 96ch 200 will likely need different motion settings. The way we split it currently is 96ch and everything else (which is due to the fact that the 96ch's have the same motor and the singles/multis share a motor) however the vast difference in friction force in the two 96ch will likely require different tuning.
This PR lays the framework for differentiating between the two different settings. It doesn't yet change any of the settings.

Test Plan and Hands on Testing

Changelog

Review requests

Risk assessment

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 24.82%. Comparing base (cb51d1b) to head (fd356e5).

Additional details and impacted files

@@           Coverage Diff           @@
##             edge   #18552   +/-   ##
=======================================
  Coverage   24.82%   24.82%           
=======================================
  Files        3273     3273           
  Lines      281047   281047           
  Branches    33831    33831           
=======================================
  Hits        69780    69780           
  Misses     211246   211246           
  Partials       21       21           

Flag	Coverage Δ
protocol-designer	19.29% <ø> (ø)
step-generation	4.37% <ø> (ø)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sfoster1]

Looks good! Let's add some tests that actually specify the 200 gantry load please