chore: improve databricks test logging

[BrendanWalsh]

Databricks test logs are overly verbose due to exception-based retry logic, obscuring contents.

• Using new retryUntil utility function which will show progress less verbosely for scenarios where we query an endpoint more frequently while waiting for completion.
• fixed a bug in tryWithRetries where the final delay passed is ignored.
• Databricks cluster id and name are printed for easier debugging upon creation.
• databricks test run name now shows notebook name instead of test1