fix(tests): use valid ULID and classification in clone-into step fixture

Resource Pydantic model requires resource_id to match the ULID pattern
^[0-9A-HJKMNP-TV-Z]{26}$ and classification to be 'physical' or
'virtual'. The test fixture used '01HANDLER0000000000000001' (invalid
ULID) and 'tool' (invalid enum), causing a ValidationError during
scenario setup that Behave reported as a traceback outside scenario.

Fixes the errored scenario in features/container_clone_into.feature:88.

ISSUES CLOSED: #7555

features/steps/container_clone_into_steps.py

@@ -305,11 +305,13 @@ def step_devcontainer_resource_with_clone_into(
     clear_lifecycle_registry()
 
     # Create a resource with clone_into in properties
+    # resource_id must be a valid ULID (Crockford Base32, 26 chars, no I/L/O/U)
+    # classification must be 'physical' or 'virtual'
     context.handler_resource = Resource(
-        resource_id="01HANDLER0000000000000001",
+        resource_id="01ARZ3NDEKTSV4RRFFQ69G5FAV",
         name="test-devcontainer",
         resource_type_name="devcontainer-instance",
-        classification="tool",
+        classification="physical",
         description="Test devcontainer for clone-into wiring",
         location="/tmp/test-workspace",
         properties={"clone_into": clone_url},
@@ -318,7 +320,7 @@ def step_devcontainer_resource_with_clone_into(
     # Set up the lifecycle tracker in DISCOVERED state with container_id pre-set
     # (simulates the state after activate_container() has run and set container_id)
     tracker = ContainerLifecycleTracker(
-        resource_id="01HANDLER0000000000000001",
+        resource_id="01ARZ3NDEKTSV4RRFFQ69G5FAV",
         current_state=ContainerLifecycleState.DISCOVERED,
         container_id=container_id,
     )