Release v0.4.0

[nfx]

• Added Volume Fixture (#72). This commit introduces a Managed Volume fixture, make_volume, to the Unity Catalog in the test suite, facilitating the creation and use of a random volume for testing purposes. The fixture, when called without arguments, generates a volume with a random name. Alternatively, specifying the name argument creates a volume with the given name, using the MANAGED volume type, and associating it with a randomly generated catalog and schema. This promotes test isolation and prevents unintended interference. Additionally, this PR resolves issue #70 and includes unit and integration tests that have been manually verified to ensure the fixture's proper functioning. The commit also demonstrates a bug fix related to table retrieval in the test_remove_after_property_table test case.

[github-actions]

❌ 38/39 passed, 1 failed, 3 skipped, 7m38s total

❌ test_managed_schema_fixture: databricks.sdk.errors.platform.BadRequest: org.apache.hadoop.hive.ql.metadata.HiveException: MetaException(message:Got exception: shaded.databricks.CLOUD_ENVbfs.org.apache.hadoop.fs.CLOUD_ENVbfs.contracts.exceptions.KeyProviderException Failure to initialize configuration for storage account labsCLOUD_ENVTEST_MOUNT_NAME.dfs.core.windows.net: Invalid configuration value detected for fs.CLOUD_ENV.account.key) (987ms)

databricks.sdk.errors.platform.BadRequest: org.apache.hadoop.hive.ql.metadata.HiveException: MetaException(message:Got exception: shaded.databricks.CLOUD_ENVbfs.org.apache.hadoop.fs.CLOUD_ENVbfs.contracts.exceptions.KeyProviderException Failure to initialize configuration for storage account labsCLOUD_ENVTEST_MOUNT_NAME.dfs.core.windows.net: Invalid configuration value detected for fs.CLOUD_ENV.account.key)
[gw0] linux -- Python 3.10.15 /home/runner/work/pytester/pytester/.venv/bin/python
17:23 DEBUG [databricks.labs.pytester.fixtures.baseline] clearing 0 schema fixtures
[gw0] linux -- Python 3.10.15 /home/runner/work/pytester/pytester/.venv/bin/python

_{Running from acceptance #121}