Adding documentation on device docs

[albi3ro]

Context:

Replacing stale #5783 [sc-53730]

Description of the Change:

Benefits:

Possible Drawbacks:

Related GitHub Issues:

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/releases/changelog-dev.md with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.39%. Comparing base (0f76651) to head (3c3746d).
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #6325   +/-   ##
=======================================
  Coverage   99.39%   99.39%           
=======================================
  Files         448      448           
  Lines       42472    42474    +2     
=======================================
+ Hits        42217    42219    +2     
  Misses        255      255           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[astralcai]

I feel that in many cases, this guide is explaining different aspects of the execution workflow without putting it in the context of how a plugin can be implemented. Many examples describes how a device should behave and how it is used in the workflow but there isn't a corresponding example to explain what a plugin developer needs to do to make it work like expected.

[astralcai]

LGTM. Thank you for doing this! 🎸

[JerryChen97]

lgtm!!!

[isaacdevlugt]

Thanks Christina! Looks good to me, just found some grammar suggestions.

[astralcai]

Not sure if these are related to the failing doc builds.