chore: Remove dependency on scanspec

[tpoliaw]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.04%. Comparing base (7b10cc3) to head (2cc9068).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1366   +/-   ##
=======================================
  Coverage   95.04%   95.04%           
=======================================
  Files          43       43           
  Lines        2783     2783           
=======================================
  Hits         2645     2645           
  Misses        138      138           

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

[ZohebShaikh]

I think this can be move to dev dependencies, but should not be remove because
this was added because scanspec plans were not running in blueapi out of the box, so we added a test to specifically test it. (When there were lot of pydantic changes that were breaking scanspec)

If this happens we will not be able to know if the latest scanspec is working with blueapi.

[tpoliaw]

This is still testing if blueapi can run scanspec scans, it's just not testing the serialization part which isn't normally used by the server.

[ZohebShaikh]

You are right that the serialisation in not used by the server, but blueapi-client does use it when it wants to run a plan.
I think after this is merge we will not be able to tell which version of scanspec blueapi-client is guaranteed to work.

[tpoliaw]

Where does the client use scanspec? Doesn't it use the JSON object directly?

[ZohebShaikh]

I might be wrong on this. But might be worth giving it a try. We can always add this back if it starts causing problems