fix: Check if plan parameter is subclass of Device

The previous check for whether a parameter was a bluesky device (and
would therefore go via the string-to-device lookup) was based on the
type being an instance of one of the bluesky protocols.

For a device that only extends `Device`, this check would return False
and the device could not be injected.

Including a check for the type being a subclass of Device allows all
device subclasses to be looked up.

Author: tpoliaw

src/blueapi/core/context.py

@@ -44,6 +44,7 @@
 
 from .bluesky_types import (
     BLUESKY_PROTOCOLS,
+    AsyncDevice,
     Device,
     Plan,
     PlanGenerator,
@@ -103,7 +104,11 @@ def qualified_generic_name(target: type) -> str:
 
 
 def is_bluesky_type(typ: type) -> bool:
-    return typ in BLUESKY_PROTOCOLS or isinstance(typ, BLUESKY_PROTOCOLS)
+    return (
+        typ in BLUESKY_PROTOCOLS
+        or isinstance(typ, BLUESKY_PROTOCOLS)
+        or issubclass(typ, AsyncDevice)
+    )
 
 
 C = TypeVar("C", covariant=True)