Thanks, Advika! your answer helped a lot.

The issue turned out to be caused by a dbt-databricks minor update. Although we had pinned the package to avoid major upgrades, the minor update still introduced the problem.

So yes, libraries was added to the cluster policy to install the dependencies, but the unexpected behavior came specifically from the minor version change.

Thank you,

Guilherme