Fix failing unit tests

[asnare]

Changes

This PR works around a behaviour change introduced by Databricks SDK v0.102.0 that causes unit tests to fail if they are using the Config class. Specifically, during __init__() the Config() class now performs a HTTP request against the host, and retries for 5 minutes if the host does not exist.

Unit tests typically fill in a bogus host, which was fine previously because initialising Config was inert and didn't trigger network calls. Now that it does, some sort of workaround (such as monkey-patching) is required.

Incidental change:

• Dependency-management for the project was out-of-date, and stopped working because the lockfile referred directly to an internal PyPi proxy that is no longer intended for use. As such the plumbing for locking dependencies was updated, and the lockfile regenerated.

Linked issues

Tests, same as: databrickslabs/blueprint#331
For Makefile, same as: databrickslabs/blueprint#392

Tests

• updated unit tests

[github-actions]

✅ 40/40 passed, 6 skipped, 14m20s total

_{Running from acceptance #253}