Remove device_factory and supporting methods

[tpoliaw]

Requires matching changes to avoid breakage:

• chore!: Remove dodal dependency blueapi#1534
• mx-bluesky changes Remove usage of device factory mx-bluesky#1732

All beamlines are now using a device manager to mark the device factories so the previous decorator and supporting code is no longer required.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.27%. Comparing base (0beeb31) to head (d2cf369).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2044      +/-   ##
==========================================
+ Coverage   99.11%   99.27%   +0.15%     
==========================================
  Files         327      327              
  Lines       12814    12595     -219     
==========================================
- Hits        12701    12504     -197     
+ Misses        113       91      -22     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[DominicOram]

clear_devices is used by mx-bluesky so this will require some changes there too. I'm not sure how significant they will be @DiamondLightSource/developers-mx-daq?

[DominicOram]

Should: Do we still need this? And the get/clear? It was my understanding that BlueAPI now handles the path provider a different way?

[rtuck99]

Hyperion is still using it because it sets its own path provider

[DominicOram]

That's annoying. Can we have BlueAPI inject the path provider into the composite so that we can avoid having the globals around?