Add support for dashboards in deployment bind/unbind commands

[anton-107]

Changes

1. Changed FindResourceByConfigKey to return dashboard resources
2. Changed deploy phase to detect dashboard recreation and request user's approval before deploying

Why

This PR adds support for dashboard resources in deployment operations, enabling users to:

• Bind experiments using databricks bundle deployment bind <mydashboard_key> <mydashboard_id>
• Unbind experiments using databricks bundle deployment unbind <mydashboard_key>

Where:

• mydashboard_key is a resource key defined in the bundle's .yml file
• mydashboard_id references an existing dashboard in the Databricks workspace

These capabilities allow for more flexible resource management of dashboards within bundles.

Tests

Added two new acceptance tests that tests bind and unbind methods together with bundle deployment and destruction, including a case of dashboard recreation

[denik]

Is there any downside for hardcoding these in acceptance_test.go if CLOUD_ENV is "" and they are not set already?

[anton-107]

the only thing i can think of - this style keeps this local to the test and does not encourage variables that are too use-case specific to be used in unrelated tests

[shreyas-goenka]

Can we fix Dashboard recreation on bind before we proceed with this? I would consider recreation of dashboards on bind + subsequent deployment to be a correctness issue.

[anton-107]

Can we fix Dashboard recreation on bind before we proceed with this? I would consider recreation of dashboards on bind + subsequent deployment to be a correctness issue.

We are not able to fix the Dashboard re-creation, as there is not API to move a dashboard to a different location without changing its ID. Instead, we will introduce a warning check for end users that a Dashboard would be re-created on deployment