Fix Direct Lake semantic model binding in Deployment Pipelines

[lk123]

When deploying Direct Lake semantic models via Deployment Pipelines, the Lakehouse source is incorrectly treated as an external SQL source. This results in broken lineage and prompts for credentials.

Even when using deployment rules to update the SQL endpoint and database ID, the semantic model does not re-bind to the Lakehouse in the target environment.

Expected behavior:
Deployment Pipelines should natively support Direct Lake re-binding, maintaining proper lineage and avoiding unnecessary credential prompts.

Current workaround:
Using the semantic-link-labs library to rebind the semantic model programmatically post-deployment.

[agusmba]

Likewise for DirectLake (OneLake) semantic models. There is no auto-binding to the equivalent lakehouse on the destination workspace nor deployment rules to manually configure the rebinding.