Add support for experiments in deployment bind/unbind commands

[anton-107]

Changes

1. Changed FindResourceByConfigKey to return experiment resources

Why

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

• Bind experiments using databricks bundle deployment bind <myexperiment_key> <experiment_id>
• Unbind experiments using databricks bundle deployment unbind <myexperiment_key>

Where:

• myexperiment_key is a resource key defined in the bundle's .yml file
• experiment_id references an existing experiment in the Databricks workspace

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

Tests

Added a new acceptance test that tests bind and unbind methods together with bundle deployment and destruction.

[andrewnester]

I know that existing tests for bind are integration tests but have you explored making new ones acceptance tests instead?

[andrewnester]

This is not related to this PR but this highlights that experiment API does not respect /Workspace prefix in name when they are created

[andrewnester]

Does this replacement setting comes from some other test? Any chance we can just disable this replacement for this test?

[anton-107]

I discovered this behavior by writing this test and seeing our Windows environments failing on it.
There is a variety of env variables that we could try to disable the replacements: https://stackoverflow.com/questions/7250130/how-to-stop-mingw-and-msys-from-mangling-path-names-given-at-the-command-line, but they are reported to causing other issues unexpectedly, so I propose to not dive into this until there are more cases that cause trouble.