lakehouse-hls-readmission should be installed using non-serverless machine learning runtime compute

[KhagayN]

1. When installing the lakehouse-hls-readmission solution accelerator with serverless compute, many issues with the codebase were encountered. The DLT pipeline failed because it was utilizing serverless compute by default. I instead needed to disable serverless for it to default to non-serverless compute. That got the DLT pipeline working, but the debugging of this was unnecessary, because if I utilized a non-serverless ML runtime cluster to install lakehouse-hls-readmission, the DLT pipeline runs successfully.

There should be clear instructions on what type of cluster to install the solution accelerator.

2. The masking function cannot be applied to a streaming table in the governance notebook.

[QuentinAmbard]

hey, fyi we're doing a full update for serverless so this should be solved in a few weeks. We had a few advanced issues that we're working on with the product, so it got a bit delayed but it's coming soon!