Currently, Zeebe definitions are saved with a string "Zeebe" as their engine. This doesn't make much sense in the context of Optimize. We should look at changing the structure/name of that field to better represent what is a data source rather than just an engine. For Zeebe definitions, we could store the prefix and partition for example

ATs:

• Process definitions store the appropriate data source import information regardless of type (Zeebe or Camunda engine)
• Current definitions are migrated to match the new structure