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

[BrendanWalsh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.62%. Comparing base (e12b0a1) to head (bdc5272).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2367      +/-   ##
==========================================
- Coverage   84.67%   84.62%   -0.06%     
==========================================
  Files         331      331              
  Lines       17180    17180              
  Branches     1544     1544              
==========================================
- Hits        14548    14539       -9     
- Misses       2632     2641       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.