feat(operators): add script operation support for DiscoverySpace

[michael-johnston]

This PR adds first-class support for inline script operations on DiscoverySpace instances, so custom sampling code can store measurements under a proper OperationResource without registering an operator plugin or going through orchestrate().

• Introduces ScriptOperatorConf - specifies a "dynamic" operator that doesn't require the operator registry
• Adds DiscoverySpace.operation_context() to create and lifecycle-manage a script operation (CREATED → STARTED → FINISHED/SUCCESS or FAIL), yielding an operation_id for use with Actuators
• Ensures script-run measurements appear in sampledEntities(), space summaries, and ado show operation commands
• Can be used to record any type of operation

Use

Combined with #169 you can now do the following to iterate over a space, make measurements synchronously, store them without ray objects.

  space = DiscoverySpace.from_stored_configuration(
                      project_context=ctx,
                      space_identifier=space_id,
                      )

  actuators = {}
  for experiment in space.measurementSpace.experiments:
      aid = experiment.actuatorIdentifier
      if aid in actuators:
          continue
      actuator_cls = registry.actuatorForIdentifier(aid)
      actuators[aid] = actuator_cls()

  with space.operation_context(
      name="direct-standard-actuator-grid",
      description="Example of iterating over a discrete space",
  ) as operation_id:
      sampler = ExplicitEntitySpaceGridSampleGenerator(mode=WalkModeEnum.SEQUENTIAL)
      request_index = 0
      for batch in sampler.entityIterator(space, batchsize=1):
          for experiment in space.measurementSpace.experiments:
              ref = experiment.reference
              actuator = actuators[ref.actuatorIdentifier]
              completed = actuator.execute(
                  entities=batch,
                  experimentReference=ref,
                  requesterid=operation_id,
                  requestIndex=request_index,
                  use_ray=False,
              )
              space.addMeasurement(completed)
              request_index += 1

Motivation

Developers want to use DiscoverySpace for sampling and result storage from custom scripts or lightweight inline operator logic, perhaps inside an existing operator. Previously this required a registered explore operator in order to create the required OperationResource to associate measurements to (measurements stored without a linked OperationResource were invisible to most ADO query paths.)

[AlessandroPomponio]

Wouldn't it be clearer to have a ConfigurationMetadata parameter instead of these three? When I read name I assumed it would've been basically the operation identifier, which felt weird to me but that's what I assumed

[michael-johnston]

🤷 no real opinion :-)

[AlessandroPomponio]

Why are these things mocked?

[michael-johnston]

Agents

[AlessandroPomponio]

I assume this serves to test a case where there's an exception after the operation id is returned. First of all, it looks a bit weird with the "boom", so I would maybe change that to be something like "exception during execution"
We also don't need to mock the store, right?

[michael-johnston]

sure