feat(api): protocol engine command for identifying module (w/ stacker implementation)

[ahiuchingau]

Overview

This PR introduces the identifyModule command to the protocol engine, allowing hardware modules to be identified by module model and module ID. Currently, the identify function is only implemented for the stacker.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 22.81%. Comparing base (14ee9f8) to head (92a2149).
Report is 5 commits behind head on edge.

Additional details and impacted files

@@             Coverage Diff             @@
##             edge   #17951       +/-   ##
===========================================
- Coverage   62.01%   22.81%   -39.21%     
===========================================
  Files        2989     2989               
  Lines      232004   232810      +806     
  Branches    20013    19751      -262     
===========================================
- Hits       143885    53116    -90769     
- Misses      87942   179683    +91741     
+ Partials      177       11      -166     

Flag	Coverage Δ
app	0.34% <ø> (-47.37%)	⬇️
protocol-designer	18.87% <ø> (ø)
step-generation	4.40% <ø> (ø)

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

see 1752 files with indirect coverage changes

🚀 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.

[ddcc4]

Drive-by comment: What will show up in the run log and in simulate if this command is used?

[ahiuchingau]

Drive-by comment: What will show up in the run log and in simulate if this command is used?

I'm not sure actually. We are planning on using this command only during a module attach flow on the app/odd. Do you think it should show up in the run log?