Add logging for each stage of the eiger arming

[olliesilvester]

Part of DiamondLightSource/mx-bluesky#1204

When the eiger fails to arm, we can't easily see exactly which part of the staging process failed, since we just see that the overall status failed. See https://graylog.diamond.ac.uk/messages/graylog-prod_7/66e85600-7912-11f0-9564-9635308342fa

This PR will give us slightly more info when the Eiger fails to arm

Instructions to reviewer on how to test:

1. Check each stage of the arming now will give a logging message

Checks for reviewer

• Would the PR title make sense to a scientist on a set of release notes
• If a new device has been added does it follow the standards
• If changing the API for a pre-existing device, ensure that any beamlines using this device have updated their Bluesky plans accordingly
• Have the connection tests for the relevant beamline(s) been run via dodal connect ${BEAMLINE}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.75%. Comparing base (2c9bbb7) to head (facf99a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1468   +/-   ##
=======================================
  Coverage   98.74%   98.75%           
=======================================
  Files         235      235           
  Lines        8626     8641   +15     
=======================================
+ Hits         8518     8533   +15     
  Misses        108      108           

☔ 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]

Minor comment but generally looks good, thanks,

[DominicOram]

Nit: Remove print statement in code