[Doc] Unify/reorganize notes in docs for resources/data sources (#4657)

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

Changes include:

* Remove not necessary `**Note**` in `->`, etc.
* Put notes about account or workspace level provider after the first
paragraph, so it's easier to understand what resource/data source is
doing, and then read the note.
* Added missing notes about account or workspace level provider
* Removed repeated notes about `authentication is not configured for
provider errors` that is more about troubleshooting than about specific
resource/data source.

## 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`
- [ ] using Go SDK
- [ ] using TF Plugin Framework

---------

Co-authored-by: vuong-nguyen <[email protected]>

Author: alexott

NEXT_CHANGELOG.md

@@ -10,6 +10,8 @@
 
 ### Documentation
 
+ * Unify/reorganize notes in docs for resources/data sources ([#4657](https://github.com/databricks/terraform-provider-databricks/pull/4657))
+
 ### Exporter
 
 ### Internal Changes

docs/data-sources/app.md

@@ -3,6 +3,8 @@ subcategory: "Apps"
 ---
 # databricks_app Data Source
 
+-> This data source can only be used with a workspace-level provider!
+
 -> This feature is in [Public Preview](https://docs.databricks.com/release-notes/release-types.html).
 
 [Databricks Apps](https://docs.databricks.com/en/dev-tools/databricks-apps/index.html) run directly on a customer’s Databricks instance, integrate with their data, use and extend Databricks services, and enable users to interact through single sign-on. This resource creates the application but does not handle app deployment, which should be handled separately as part of your CI/CD pipeline.

docs/data-sources/apps.md

@@ -3,6 +3,8 @@ subcategory: "Apps"
 ---
 # databricks_apps Data Source
 
+-> This data source can only be used with a workspace-level provider!
+
 -> This feature is in [Public Preview](https://docs.databricks.com/release-notes/release-types.html).
 
 [Databricks Apps](https://docs.databricks.com/en/dev-tools/databricks-apps/index.html) run directly on a customer’s Databricks instance, integrate with their data, use and extend Databricks services, and enable users to interact through single sign-on. This resource creates the application but does not handle app deployment, which should be handled separately as part of your CI/CD pipeline.

docs/data-sources/aws_assume_role_policy.md

@@ -6,6 +6,8 @@ subcategory: "Deployment"
 
 This data source constructs necessary AWS STS assume role policy for you.
 
+-> This data source can be used with an account or workspace-level provider.
+
 ## Example Usage
 
 End-to-end example of provisioning Cross-account IAM role with [databricks_mws_credentials](../resources/mws_credentials.md) and [aws_iam_role](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_role):

docs/data-sources/aws_bucket_policy.md

@@ -5,6 +5,8 @@ subcategory: "Deployment"
 
 This datasource configures a simple access policy for AWS S3 buckets, so that Databricks can access data in it.
 
+-> This data source can be used with an account or workspace-level provider.
+
 ## Example Usage
 
 ```hcl

docs/data-sources/aws_crossaccount_policy.md

@@ -3,10 +3,10 @@ subcategory: "Deployment"
 ---
 # databricks_aws_crossaccount_policy Data Source
 
--> **Note** This data source can only be used with an account-level provider!
-
 This data source constructs necessary AWS cross-account policy for you, which is based on [official documentation](https://docs.databricks.com/administration-guide/account-api/iam-role.html#language-Your%C2%A0VPC,%C2%A0default).
 
+-> This data source can be used with an account or workspace-level provider.
+
 ## Example Usage
 
 For more detailed usage please see [databricks_aws_assume_role_policy](aws_assume_role_policy.md) or [databricks_aws_s3_mount](../resources/mount.md) pages.

docs/data-sources/aws_unity_catalog_assume_role_policy.md

@@ -3,10 +3,12 @@ subcategory: "Deployment"
 ---
 # databricks_aws_unity_catalog_assume_role_policy Data Source
 
--> **Note** This resource has an evolving API, which may change in future versions of the provider. Please always consult [latest documentation](https://docs.databricks.com/data-governance/unity-catalog/get-started.html#configure-a-storage-bucket-and-iam-role-in-aws) in case of any questions.
-
 This data source constructs the necessary AWS Unity Catalog assume role policy for you.
 
+-> This data source can be used with an account or workspace-level provider.
+
+-> This data source has an evolving API, which may change in future versions of the provider. Please always consult [latest documentation](https://docs.databricks.com/data-governance/unity-catalog/get-started.html#configure-a-storage-bucket-and-iam-role-in-aws) in case of any questions.
+
 ## Example Usage
 
 ```hcl

docs/data-sources/aws_unity_catalog_policy.md

@@ -3,10 +3,12 @@ subcategory: "Deployment"
 ---
 # databricks_aws_unity_catalog_policy Data Source
 
--> **Note** This resource has an evolving API, which may change in future versions of the provider. Please always consult [latest documentation](https://docs.databricks.com/data-governance/unity-catalog/get-started.html#configure-a-storage-bucket-and-iam-role-in-aws) in case of any questions.
-
 This data source constructs the necessary AWS Unity Catalog policy for you.
 
+-> This data source can be used with an account or workspace-level provider.
+
+-> This data source has an evolving API, which may change in future versions of the provider. Please always consult [latest documentation](https://docs.databricks.com/data-governance/unity-catalog/get-started.html#configure-a-storage-bucket-and-iam-role-in-aws) in case of any questions.
+
 ## Example Usage
 
 ```hcl

docs/data-sources/budget_policies.md

@@ -2,10 +2,10 @@
 subcategory: "FinOps"
 ---
 # databricks_budget_policies Data Source
-This data source can be used to fetch the list of budget policies. 
 
--> **Note** This data source can only be used with an account-level provider!
+This data source can be used to fetch the list of budget policies. 
 
+-> This data source can only be used with an account-level provider!
 
 ## Example Usage
 
@@ -26,4 +26,4 @@ data "databricks_budget_policies" "all" {
 
 Data source exposes the following attributes:
 
-- `budget_policies` - The list of budget policy.
+- `budget_policies` - The list of budget policy.

docs/data-sources/budget_policy.md

@@ -2,9 +2,10 @@
 subcategory: "FinOps"
 ---
 # databricks_budget_policy Data Source
+
 This data source can be used to get a single budget policy. 
 
--> **Note** This data source can only be used with an account-level provider!
+-> This data source can only be used with an account-level provider!
 
 ## Example Usage
 
@@ -27,4 +28,4 @@ Data source allows you to get a budget policy by the following attribute
 Data source exposes the following attributes:
 
 - `policy_id` - The id of the budget policy.
-- `policy_name` - The name of the budget policy.
+- `policy_name` - The name of the budget policy.