Investigate merging the `physicalai-studio-plugin` back into `physicalai`

[MarkRedeman]

The physicalai-studio-plugin exposes additional interfaces that are used by Studio for its robot plugin implementation.
Its important part is:

@dataclass
class RobotCatalogDefinition(Generic[_PayloadT]):
    """Complete definition of a plugin robot type for Studio registration."""

    type: str
    display_name: str
    role: Literal["follower", "leader"]
    robot_builder: BuildRobotCallable | None = None
    robot_payload: _PayloadModelT | None = None
    asset: RobotAsset | None = None

    adapter_options: RobotAdapterOptions = field(default_factory=RobotAdapterOptions)
    probe: RobotProbe[_PayloadT] | None = None

which helps studio in building a robot driver, constructing a UI from the payload schema.
The RobotProbe and RobotAsset fields are both fields that could be beneficial to the physicalai runtime itself.

@maxxgx can you also look into removing the adapter_options. Before these were used in studio's runtime, but I believe that they may now be ignored..?