combine lakehouse and sql endpoint items

[mim788]

This is purely for aesthetic and usability reasons.

Now that a default semantic model is no longer generated when creating a new Lakehouse, could we consider streamlining the user experience by merging the Lakehouse and its SQL analytics endpoint into a single item?

At the moment, having them listed separately feels a bit redundant and visually inconsistent. Consolidating them would make the interface cleaner and more intuitive.

[masonpiwonka]

When both Lakehouse and SQL endpoint are open with the same name, the item icons of what you have recently opened are hard to decipher. This often leads to extra clicks because I selected the wrong item. @mim788, I would love if this made only one item on the left side of the page. This aspect also feels redundant.

[ToddChitt]

I suggested something similar but cannot find it. EVERY Lakehouse has the SAME SQL Analytic Endpoint, so why are we showing said SQL Analytic Endpoint under every lakehouse? Seems "Department of Redundancy Department". Plus, once I have captured that endpoint info and put it into my SSMS Registered Servers, I no longer need to see that info every again. It should be hidden behind the ellipsis to make more room on the screen.