Custom Databricks-prefixed plugin types should use standard plugin UI

[Bionic711]

Issue

Custom plugin types with Databricks-prefixed names, such as databricks_table_dscmo, can be classified like the built-in Databricks action during action type discovery or visual rendering. These custom plugin types should use the standard plugin UI unless their type is exactly databricks or databricks_table.

Steps to Reproduce

1. Add or discover a custom plugin type named databricks_table_dscmo.
2. Open the action creation or management UI.
3. Observe how the plugin type is classified, displayed, or configured.

Expected Behavior

Custom Databricks-prefixed plugin types load the standard plugin configuration UI and standard visual treatment unless the type is exactly databricks or databricks_table.

Actual Behavior

Broad substring matching can make custom Databricks-prefixed plugin types inherit built-in Databricks discovery defaults or visual treatment.

Impact

Admins and users creating custom plugin types can see the wrong UI path, causing confusion and potentially incorrect configuration requirements.

Notes

Implemented fix in version 0.250.103 narrows Databricks discovery and icon classification to exact built-in types. Regression coverage scaffolds a temporary fake databricks_table_dscmo plugin, definition, and schema files to verify discovery and settings merge stay on the standard path.

Related files:

• application/single_app/functions_databricks_operations.py
• application/single_app/route_backend_plugins.py
• application/single_app/static/js/workspace/view-utils.js
• functional_tests/test_plugin_type_discovery_custom_databricks.py
• docs/explanation/fixes/CUSTOM_DATABRICKS_PLUGIN_DISCOVERY_FIX.md