[dagster-databricks] fix issue with op name generation (#20330)

Fixes an issue where if an op name provided, that op name would be used
directly for all tasks, leading to name collision issues.

Now we just use it as a prefix so names can stay unique.
## Test Plan

## Changelog

> If a changelog entry is required, replace this section with the
desired entry.
>
> By default, no changelog entry will be produced for internal PRs.

Synced-From-Internal

GitOrigin-RevId: 62292313fec1b837930ac537572e2dfe2b935826

Author: OwenKephart

python_modules/libraries/dagster-databricks/dagster_databricks/components/databricks_asset_bundle/component.py

@@ -246,11 +246,10 @@ def build_defs(self, context: ComponentLoadContext) -> Definitions:
 
         databricks_assets = []
         for task_key, asset_specs in self.asset_specs_by_task_key.items():
+            op_prefix = self.op.name if self.op and self.op.name else "databricks"
 
             @multi_asset(
-                name=self.op.name
-                if self.op and self.op.name
-                else f"databricks_{task_key}_multi_asset_{component_defs_path_as_python_str}",
+                name=f"{op_prefix}_{task_key}_multi_asset_{component_defs_path_as_python_str}",
                 specs=asset_specs,
                 can_subset=False,
                 op_tags=self.op.tags if self.op else None,