…concept into docs

…concept into docs

Bumps [github.com/Azure/go-autorest/autorest](https://github.com/Azure/go-autorest) from 0.11.9 to 0.11.12.
- [Release notes](https://github.com/Azure/go-autorest/releases)
- [Changelog](https://github.com/Azure/go-autorest/blob/master/CHANGELOG.md)
- [Commits](Azure/go-autorest@autorest/v0.11.9...autorest/v0.11.12)

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [github.com/hashicorp/go-retryablehttp](https://github.com/hashicorp/go-retryablehttp) from 0.6.7 to 0.6.8.
- [Release notes](https://github.com/hashicorp/go-retryablehttp/releases)
- [Commits](hashicorp/go-retryablehttp@v0.6.7...v0.6.8)

Signed-off-by: dependabot[bot] <support@github.com>

…e value

* `network_error_messages` and `verify_workspace_runnning` from `databricks_mws_workspaces` is deprecated and going to be removed in 0.3.
* `error_messages` from `databricks_mws_networks` are deprecated and would be removed in 0.3.
* `ebs_volume_type` and `azure_disk_volume_type` from `databricks_instance_pool` is going to be moved to `disk_type` sub-block in 0.3, which means you'll slightly have to modify configuration while migrating to 0.3.

* `databricks_notebook` & `databricks_dbfs_file` field `content` is deprecated and would be renamed to `content_base64` to further increase clarity.
* `databricks_dbfs_file` has got `content`, `content_b64_md5`, `overwrite`, `mkdirs`, `validate_remote_file` fields deprecated and they will be removed in the next version, where critical code path will be shared with `databricks_notebook`.

So this will offload ID format maintainance to SDK

…-databricks-1 into pr/386