[Doc] Correctly use native markdown callouts supported by TF Registry (#4073)

## Changes
<!-- Summary of your changes that are easy to understand -->

TF registry supports a [number of special
callouts](https://developer.hashicorp.com/terraform/registry/providers/docs#callouts)
to highlight paragraphs. These callouts automatically add text like
`**Note**` or `**Warning**` so we don't need to add them ourselves.

Also, make consistent usage of informational callouts (`->`), important
callouts (`~>`, that uses yellow background for paragraph), and warnings
(`!>`).

## Tests
<!-- 
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->

- [ ] `make test` run locally
- [x] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] relevant acceptance tests are passing
- [ ] using Go SDK

Author: alexott

docs/resources/access_control_rule_set.md

@@ -4,13 +4,13 @@ subcategory: "Security"
 
 # databricks_access_control_rule_set Resource
 
--> **Note** This resource can be used with an account or workspace-level provider.
+-> This resource can be used with an account or workspace-level provider.
 
 This resource allows you to manage access rules on Databricks account level resources. For convenience we allow accessing this resource through the Databricks account and workspace.
 
--> **Note** Currently, we only support managing access rules on service principal, group and account resources through `databricks_access_control_rule_set`.
+-> Currently, we only support managing access rules on service principal, group and account resources through `databricks_access_control_rule_set`.
 
--> **Warning** `databricks_access_control_rule_set` cannot be used to manage access rules for resources supported by [databricks_permissions](permissions.md). Refer to its documentation for more information.
+!> `databricks_access_control_rule_set` cannot be used to manage access rules for resources supported by [databricks_permissions](permissions.md). Refer to its documentation for more information.
 
 ## Service principal rule set usage
 

docs/resources/artifact_allowlist.md

@@ -3,10 +3,9 @@ subcategory: "Unity Catalog"
 ---
 # databricks_artifact_allowlist Resource
 
--> **Note**
-  It is required to define all allowlist for an artifact type in a single resource, otherwise Terraform cannot guarantee config drift prevention.
+~> It is required to define all allowlist for an artifact type in a single resource, otherwise Terraform cannot guarantee config drift prevention.
 
--> **Note** This resource can only be used with a workspace-level provider!
+-> This resource can only be used with a workspace-level provider!
 
 In Databricks Runtime 13.3 and above, you can add libraries and init scripts to the allowlist in UC so that users can leverage these artifacts on compute configured with shared access mode.
 

docs/resources/automatic_cluster_update_setting.md

@@ -4,7 +4,7 @@ subcategory: "Settings"
 
 # databricks_automatic_cluster_update_workspace_setting Resource
 
--> **Note** This resource can only be used with a workspace-level provider!
+-> This resource can only be used with a workspace-level provider!
 
 The `databricks_automatic_cluster_update_workspace_setting` resource allows you to control whether automatic cluster update is enabled for the current workspace. By default, it is turned off. Enabling this feature on a workspace requires that you add the Enhanced Security and Compliance add-on.
 

docs/resources/budget.md

@@ -3,9 +3,9 @@ subcategory: "FinOps"
 ---
 # databricks_budget Resource
 
--> **Note** Initialize provider with `alias = "account"`, and `host` pointing to the account URL, like, `host = "https://accounts.cloud.databricks.com"`. Use `provider = databricks.account` for all account-level resources.
+-> Initialize provider with `alias = "account"`, and `host` pointing to the account URL, like, `host = "https://accounts.cloud.databricks.com"`. Use `provider = databricks.account` for all account-level resources.
 
--> **Public Preview** This feature is in [Public Preview](https://docs.databricks.com/release-notes/release-types.html).
+-> This feature is in [Public Preview](https://docs.databricks.com/release-notes/release-types.html).
 
 This resource allows you to manage [Databricks Budgets](https://docs.databricks.com/en/admin/account-settings/budgets.html).
 

docs/resources/catalog.md

@@ -3,7 +3,7 @@ subcategory: "Unity Catalog"
 ---
 # databricks_catalog Resource
 
--> **Note** This resource can only be used with a workspace-level provider!
+-> This resource can only be used with a workspace-level provider!
 
 Within a metastore, Unity Catalog provides a 3-level namespace for organizing data: Catalogs, Databases (also called Schemas), and Tables / Views.
 

docs/resources/catalog_workspace_binding.md

@@ -3,17 +3,15 @@ subcategory: "Unity Catalog"
 ---
 # databricks_catalog_workspace_binding Resource
 
--> **NOTE**This resource has been deprecated and will be removed soon. Please use the [databricks_workspace_binding resource](./workspace_binding.md) instead.
+~> This resource has been deprecated and will be removed soon. Please use the [databricks_workspace_binding resource](./workspace_binding.md) instead.
 
 If you use workspaces to isolate user data access, you may want to limit catalog access to specific workspaces in your account, also known as workspace-catalog binding
 
 By default, Databricks assigns the catalog to all workspaces attached to the current metastore. By using `databricks_catalog_workspace_binding`, the catalog will be unassigned from all workspaces and only assigned explicitly using this resource.
 
--> **Note**
-  To use this resource the catalog must have its isolation mode set to `ISOLATED` in the [`databricks_catalog`](https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/catalog#isolation_mode) resource. Alternatively, the isolation mode can be set using the UI or API by following [this guide](https://docs.databricks.com/data-governance/unity-catalog/create-catalogs.html#configuration).
+-> To use this resource the catalog must have its isolation mode set to `ISOLATED` in the [`databricks_catalog`](https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/catalog#isolation_mode) resource. Alternatively, the isolation mode can be set using the UI or API by following [this guide](https://docs.databricks.com/data-governance/unity-catalog/create-catalogs.html#configuration).
 
--> **Note**
-  If the catalog's isolation mode was set to `ISOLATED` using Terraform then the catalog will have been automatically bound to the workspace it was created from.
+-> If the catalog's isolation mode was set to `ISOLATED` using Terraform then the catalog will have been automatically bound to the workspace it was created from.
 
 ## Example Usage
 

docs/resources/cluster.md

@@ -5,7 +5,7 @@ subcategory: "Compute"
 
 This resource allows you to manage [Databricks Clusters](https://docs.databricks.com/clusters/index.html).
 
--> **Note** In case of [`Cannot access cluster ####-######-####### that was terminated or unpinned more than 30 days ago`](https://github.com/databricks/terraform-provider-databricks/issues/1197#issuecomment-1069386670) errors, please upgrade to v0.5.5 or later. If for some reason you cannot upgrade the version of provider, then the other viable option to unblock the apply pipeline is [`terraform state rm path.to.databricks_cluster.resource`](https://www.terraform.io/cli/commands/state/rm) command.
+-> In case of [`Cannot access cluster ####-######-####### that was terminated or unpinned more than 30 days ago`](https://github.com/databricks/terraform-provider-databricks/issues/1197#issuecomment-1069386670) errors, please upgrade to v0.5.5 or later. If for some reason you cannot upgrade the version of provider, then the other viable option to unblock the apply pipeline is [`terraform state rm path.to.databricks_cluster.resource`](https://www.terraform.io/cli/commands/state/rm) command.
 
 ```hcl
 data "databricks_node_type" "smallest" {
@@ -130,7 +130,7 @@ resource "databricks_cluster" "single_node" {
 
 ### (Legacy) High-Concurrency clusters
 
--> **Note** This is a legacy cluster type, not related to the real serverless compute. See [Clusters UI changes and cluster access modes](https://docs.databricks.com/archive/compute/cluster-ui-preview.html#legacy) for information on what access mode to use when creating new clusters.
+~> This is a legacy cluster type, not related to the real serverless compute. See [Clusters UI changes and cluster access modes](https://docs.databricks.com/archive/compute/cluster-ui-preview.html#legacy) for information on what access mode to use when creating new clusters.
 
 To create High-Concurrency cluster, following settings should be provided:
 
@@ -163,7 +163,7 @@ resource "databricks_cluster" "cluster_with_table_access_control" {
 
 To install libraries, one must specify each library in a separate configuration block. Each different type of library has a slightly different syntax. It's possible to set only one type of library within one config block. Otherwise, the plan will fail with an error.
 
--> **Note** Please consider using [databricks_library](library.md) resource for a more flexible setup.
+-> Please consider using [databricks_library](library.md) resource for a more flexible setup.
 
 Installing JAR artifacts on a cluster. Location can be anything, that is DBFS or mounted object store (s3, adls, ...)
 
@@ -484,7 +484,7 @@ resource "databricks_cluster" "this" {
 
 ### cluster_mount_info blocks (experimental)
 
--> **Note** The underlying API is experimental and may change in the future.
+~> The underlying API is experimental and may change in the future.
 
 It's possible to mount NFS (Network File System) resources into the Spark containers inside the cluster.  You can specify one or more `cluster_mount_info` blocks describing the mount. This block has following attributes:
 

docs/resources/compliance_security_profile_setting.md

@@ -4,9 +4,9 @@ subcategory: "Settings"
 
 # databricks_compliance_security_profile_workspace_setting Resource
 
--> **Note** This resource can only be used with a workspace-level provider!
+-> This resource can only be used with a workspace-level provider!
 
--> **Note** This setting can NOT be disabled once it is enabled.
+~> This setting can NOT be disabled once it is enabled.
 
 The `databricks_compliance_security_profile_workspace_setting` resource allows you to control whether to enable the 
 compliance security profile for the current workspace. Enabling it on a workspace is permanent. By default, it is 

docs/resources/connection.md

@@ -3,7 +3,7 @@ subcategory: "Unity Catalog"
 ---
 # databricks_connection (Resource)
 
--> **Note** This resource can only be used with a workspace-level provider!
+-> This resource can only be used with a workspace-level provider!
 
 Lakehouse Federation is the query federation platform for Databricks. Databricks uses Unity Catalog to manage query federation. To make a dataset available for read-only querying using Lakehouse Federation, you create the following:
 

docs/resources/dbfs_file.md

@@ -49,7 +49,7 @@ resource "databricks_library" "app" {
 
 ## Argument Reference
 
--> **Note** DBFS files would only be changed, if Terraform stage did change. This means that any manual changes to managed file won't be overwritten by Terraform, if there's no local change.
+-> DBFS files would only be changed, if Terraform stage did change. This means that any manual changes to managed file won't be overwritten by Terraform, if there's no local change.
 
 The following arguments are supported: