[BUG] Have Databricks Connect match the attached cluster version's DBR

[nsenno-dbr]

Describe the bug
Our documentation implies that the version of Databricks Connect must match the version of the DBR of the cluster it is trying to connect with.

See for example here

However, it seems that the Databricks VS code extension defaults to installing databricks-connect==13.3.x regardless of what the DBR of the associated cluster is. It would be good to have parity between the DBR version and the local version of databricks connect both to ensure full functionality and to prevent confusion with our documentation.

To Reproduce
Steps to reproduce the behavior:

1. Create a new databricks project with associated virtual environment
2. Create a single user cluster with DBR higher and 13.x (note I haven't tried this on shared clusters)
3. Authenticate to the Databricks workspace using the VS code integration
4. When prompted, accept to download databricks connect
5. Compare the versions of databricks connect with the associated clusters DBR

Screenshots
If applicable, add screenshots to help explain your problem.

System information:
Paste the output ot the Help: About command (CMD-Shift-P).

Version: 1.92.2 (Universal)
Commit: fee1edb8d6d72a0ddff41e5f71a671c23ed924b9
Date: 2024-08-14T17:29:30.058Z (1 mo ago)
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0

7. Databricks Extension Version

v2.4.5

Databricks Extension Logs
Please attach the databricks extension logs

I think this link might be broken. It doesn't discuss sending usage logs

Additional context
See slack thread here. It seems that the version of databricks connect has to be the same or lower than the associated cluster's DBR, but this can cause confusion since I don't believe it's in our public documentation.