Add supported backends attribute to stages

Is your feature request related to a problem? Please describe.
Currently Curator supports the Xenna, RayData and RayActorPool backend. However some stages especially in deduplication are compatible with the ActorPool backend only and trying to run them with different backend may lead to unexpected behavior or errors.

Describe the solution you'd like
Implemented a supported_backends attribute that defaults to xenna & ray data (possibly even ray actor pool).
Specific stages that only support a subset can choose to override these.

The execution of a pipeline should also compare the supported backends with the current executing backend to ensure that the pipeline can be run or raise an error accordingly.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Start by locating the stage definitions, deduplication stages, and pipeline execution path, then trace how the current backend is selected. Define the supported backend behavior for Xenna, RayData, and RayActorPool, identify stages that need overrides, and verify that incompatible pipeline/backend combinations are rejected.