Legacy device facade class

[albi3ro]

Context:

We currently have to maintain logic for interacting with two separate device interfaces. This adds extra maintainence, and creates a lot more paths where things can go wrong or get confusing.

Given the number of low-priority plugins that follow the legacy device interface that we probably won't get around to updating, we probably won't be able to get rid of the legacy device interface any time soon. But we can isolate it and limit it's scope.

Description of the Change:

Adds a LegacyDeviceFacade class that maps a device from the old device interface to the new device interface.

Benefits:

Possible Drawbacks:

Related GitHub Issues:

[sc-58353]

[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.65%. Comparing base (b7675ca) to head (42ec3c0).
Report is 299 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5927      +/-   ##
==========================================
- Coverage   99.66%   99.65%   -0.01%     
==========================================
  Files         428      429       +1     
  Lines       41182    41124      -58     
==========================================
- Hits        41042    40983      -59     
- Misses        140      141       +1     

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

[Shiro-Raven]

LGTM! Next up is figuring out how to keep testing for device switching when DQ.Legacy is gone