Use SparkSQL without Default Lakehouse

[frithjof_v]

Make it possible to write SparkSQL without having a Default Lakehouse.

With 3- or 4- part naming, i.e.

[workspace].[lakehouse].[schema].[table] 

there should be no need to attach a Lakehouse in order to use SparkSQL.

Needing to attach a Lakehouse is annoying and adds extra complexity.

[raym85]

Oh nice! this is a good one! Agreed it can be a pain, especially when merging from feature branch to main. Seems to work well with deployment pipelines though.

[BHouston1]

Not a bad idea on the 4-part naming, but I could see an issue if a workspace is renamed and this breaks notebooks. I think that shortcuts are designed to solve for this, but then unfortunately you would need a default lakehouse before you can use them...